mongodb-runner
The easiest way to test your code against MongoDB Server
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): Handoff to MongoDB devtools org account; repo/author metadata unchanged and official. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is MongoDB org account; consistent with legit transfer. | ai | |
| provenance | no-provenance | AI (provenance): Established MongoDB org package; lack of Sigstore attestation is a process gap, not a security risk for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): MongoDB org maintainer 'durran' legitimately owns many similarly-named packages; not spam. | ai | |
| phantom-deps | phantom-dep:@mongodb-js/saslprep | AI (phantom-deps): Declared as runtime dep and referenced in config; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 6.8.4 | 9 / 19 | |
| 6.8.3 | 9 / 19 | |
| 6.8.2 | 9 / 19 | |
| 6.8.1 | 9 / 19 | |
| 6.8.0 | 9 / 19 | |
| 6.7.13 | 9 / 19 | |
| 6.7.12 | 9 / 19 | |
| 6.7.11 | 9 / 19 | |
| 6.7.10 | 9 / 19 | |
| 6.7.9 | 9 / 19 | |
| 6.7.8 | 9 / 19 | |
| 6.7.7 | 9 / 19 | |
| 6.7.6 | 8 / 19 | |
| 6.7.5 | 8 / 19 | |
| 6.7.4 | 8 / 19 | |
| 6.7.3 | 8 / 19 | |
| 6.7.2 | 8 / 19 | |
| 6.7.1 | 8 / 19 | |
| 6.7.0 | 8 / 19 | |
| 6.6.1 | 8 / 19 | |
| 6.6.0 | 8 / 19 | |
| 6.5.4 | 8 / 19 | |
| 6.5.3 | 8 / 19 | |
| 6.5.2 | 8 / 19 | |
| 6.5.1 | 8 / 19 | |
| 6.4.0 | 8 / 19 | |
| 6.3.0 | 8 / 19 | |
| 6.2.0 | 7 / 19 | |
| 6.1.0 | 7 / 19 | |
| 6.0.0 | 6 / 19 |
v6.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.3
2 findingsThis version was published by a different npm account than previous versions on 2026-07-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.1
2 findings[Accepted risk] Package 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-25, 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.