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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 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.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.