feat: maintainer/publisher signals (v0.5.0)#5
Merged
Conversation
Adds a checker that pulls the npm packument and emits two signals when takeover patterns are visible in the publish history. - new-publisher (medium): the latest release was published by an account that did not publish any of the first three releases, and the package is older than 180 days. Mirrors the event-stream 2018 attack pattern. - sole-maintainer (low): only one maintainer is registered — informational bus-factor signal, not a vulnerability. The check is npm-only for now; PyPI's JSON API does not expose comparable per-version uploader history, so a future iteration would need a different data source for that ecosystem. - New MaintainerSignal type (two patterns, two risk levels) - --no-maintainer CLI flag and matching action input - 10 new tests; bumps version to 0.5.0 Smoke-verified end-to-end against event-stream@4.0.1 (flags both new-publisher and sole-maintainer → medium) versus express@4.18.2 (consistent publishing history, multiple maintainers → clean). Co-Authored-By: Claude Opus 4.7 <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
Adds a checker that pulls the npm packument and emits two signals when takeover patterns are visible in the publish history.
new-publisher(medium) — the latest release was published by an account that did not publish any of the first three releases, and the package is older than 180 days. Mirrors the event-stream 2018 attack pattern: long-running package, sudden new face on the most recent publish.sole-maintainer(low) — only one maintainer registered on the package. Informational bus-factor signal, not a vulnerability.Both can fire from a single packument fetch. The check is npm-only for now; PyPI's JSON API doesn't expose comparable per-version uploader history.
MaintainerSignaltype--no-maintainerCLI flag + matchingno-maintaineraction inputSmoke test
Real-world validation against the historically-compromised
event-streampackage:ossrisk now detects the exact pattern that the 2018 attack exhibited.
Test plan
npm test— 10 new tests, 101 total, all greennpm run build— cleanevent-stream@4.0.1(both signals fire) andexpress@4.18.2(clean)🤖 Generated with Claude Code