@mongodb-js/signing-utils
Utilities for signing packages in CI with Garasign.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Likely internal CI account rotation; no code changes accompany the publisher switch. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mcasimir_mdb appears to be a renamed account of mcasimir within MongoDB org; not an external takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with maintainer-added for same person (account rename); not a hostile removal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): MongoDB devtools monorepo packages share templated names by design; not spam. | ai | |
| phantom-deps | phantom-dep:@types/ssh2 | AI (phantom-deps): @types/ssh2 is a runtime dep here (type stubs bundled with ssh2 usage); phantom-dep false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.5.13 | 3 / 17 | |
| 0.5.12 | 3 / 17 | |
| 0.5.11 | 3 / 17 | |
| 0.5.10 | 3 / 17 | |
| 0.5.9 | 3 / 17 | |
| 0.5.8 | 3 / 17 | |
| 0.5.7 | 3 / 17 | |
| 0.5.6 | 3 / 17 | |
| 0.5.5 | 3 / 17 | |
| 0.5.4 | 3 / 17 | |
| 0.5.3 | 3 / 17 | |
| 0.5.0 | 3 / 17 | |
| 0.4.4 | 3 / 17 | |
| 0.4.3 | 3 / 17 | |
| 0.4.2 | 3 / 17 | |
| 0.4.1 | 3 / 17 | |
| 0.4.0 | 3 / 17 | |
| 0.3.9 | 3 / 17 | |
| 0.3.8 | 3 / 17 | |
| 0.3.7 | 3 / 17 | |
| 0.3.6 | 3 / 17 | |
| 0.3.5 | 3 / 17 | |
| 0.3.4 | 3 / 17 |
v0.5.13
2 findingsThis version was published by a different npm account than previous versions on 2026-07-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gribnoysup) than the most recent previously approved version (devtoolsbot) on 2026-06-30, but gribnoysup is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.