chore(trust): npm provenance attestation + privacy policy + unknown-server FAQ#320
Merged
Conversation
…erver FAQ Why: installing docguard-cli through an AI agent (Claude Code) trips the default unknown-package/unknown-MCP legitimacy check. Two of the three trust signals it can verify were missing: - release.yml publish-npm: `npm publish --provenance` + OIDC id-token permission — every future tarball carries a Sigstore attestation binding it to this repo's GitHub Actions build. - PRIVACY.md: DocGuard collects nothing; all analysis local; the three explicit user-initiated outbound paths enumerated. Ships in the npm package (files list) and satisfies the Anthropic Connectors Directory hard requirement (missing policy = instant rejection). - README: Privacy & Supply Chain section; FAQ: why agents flag unknown servers + how to pre-trust (.mcp.json / Always allow / managed settings). - .agent skill copies version-synced to 0.33.0 (missed the release PR). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
npm 11 auto-corrects these at publish with a warning ('bin script name
was invalid and removed' — the published result was fine under npm 10,
but bug-198 precedent says npm 11 turns lenient warnings fatal). Fixed
at the source: bin without the ./ prefix, repository.url in canonical
git+…git form.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the trust gaps behind "DocGuard is unknown, needs a legitimacy check" when installing via an AI agent:
publish-npmjob now runsnpm publish --provenancewithid-token: write— every future release tarball carries a Sigstore attestation binding it to this repo's GitHub Actions build (verifiable by npm's Provenance badge, Claude Code's unknown-package check, socket.dev)..mcp.json, Always allow, managed settings)..agentskill copies version-synced to 0.33.0 (missed the release PR).Takes effect on the next release (provenance applies at publish time).
Test plan
🤖 Generated with Claude Code