@mongosh/shell-api
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; sparse README and no keywords are expected for scoped workspace packages. | ai | |
| provenance | no-provenance | AI (provenance): Established MongoDB org package; lack of Sigstore provenance is consistent across all versions. | ai | |
| dependencies | unvetted-dep:@mongosh/i18n | AI (dependencies): Sibling @mongosh/* monorepo package from the same trusted publisher. | ai | |
| dependencies | unvetted-dep:@mongosh/arg-parser | AI (dependencies): Sibling @mongosh/* monorepo package from the same trusted publisher. | ai | |
| dependencies | unvetted-dep:@mongosh/shell-bson | AI (dependencies): Sibling @mongosh/* monorepo package from the same trusted publisher. | ai | |
| dependencies | unvetted-dep:@mongosh/service-provider-core | AI (dependencies): Sibling @mongosh/* monorepo package from the same trusted publisher. | ai | |
| dependencies | unvetted-dep:mongodb-redact | AI (dependencies): MongoDB-js ecosystem package; expected dependency for this shell API package. | ai | |
| dependencies | unvetted-dep:mongodb-schema | AI (dependencies): MongoDB-js ecosystem package; expected dependency for this shell API package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.1.9 | 7 / 15 | |
| 5.1.7 | 7 / 15 | |
| 5.1.6 | 7 / 15 | |
| 5.1.4 | 7 / 15 | |
| 5.1.0 | 7 / 15 | |
| 5.0.1 | 7 / 14 | |
| 5.0.0 | 7 / 14 | |
| 3.29.1 | 7 / 14 | |
| 3.29.0 | 9 / 12 | |
| 3.28.0 | 9 / 12 | |
| 3.26.2 | 10 / 12 | |
| 3.26.1 | 10 / 12 |
v5.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.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.
v3.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.29.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.
v3.28.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.
v3.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.