@mongodb-js/mongodb-constants
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): MongoDB org-wide shift to devtools-npm-user CI account; no material diff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consolidation to org CI publisher account; benign transition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): MongoDB-js monorepo package; templated naming and sparse README are expected for internal utility packages in this org. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 0.34.2 | 1 / 19 | |
| 0.34.1 | 1 / 19 | |
| 0.33.0 | 1 / 19 | |
| 0.32.1 | 1 / 19 | |
| 0.31.0 | 1 / 19 | |
| 0.30.0 | 1 / 19 | |
| 0.29.0 | 1 / 19 | |
| 0.28.0 | 1 / 19 | |
| 0.27.0 | 1 / 19 | |
| 0.26.0 | 1 / 19 | |
| 0.25.1 | 1 / 19 | |
| 0.25.0 | 1 / 19 | |
| 0.24.2 | 1 / 19 | |
| 0.24.1 | 1 / 19 | |
| 0.24.0 | 1 / 19 | |
| 0.23.2 | 1 / 19 | |
| 0.23.1 | 1 / 19 | |
| 0.23.0 | 1 / 19 | |
| 0.22.1 | 1 / 19 | |
| 0.22.0 | 1 / 19 | |
| 0.21.2 | 1 / 19 | |
| 0.21.1 | 1 / 19 | |
| 0.21.0 | 1 / 19 | |
| 0.20.2 | 1 / 19 | |
| 0.20.1 | 1 / 19 | |
| 0.20.0 | 1 / 19 | |
| 0.19.5 | 1 / 19 | |
| 0.19.4 | 1 / 19 | |
| 0.19.3 | 1 / 19 | |
| 0.19.0 | 1 / 19 | |
| 0.18.0 | 1 / 19 | |
| 0.17.1 | 1 / 19 | |
| 0.17.0 | 1 / 19 | |
| 0.16.1 | 1 / 19 | |
| 0.16.0 | 1 / 19 | |
| 0.14.0 | 1 / 19 | |
| 0.12.2 | 1 / 18 | |
| 0.12.1 | 1 / 18 | |
| 0.12.0 | 1 / 18 | |
| 0.11.3 | 1 / 18 | |
| 0.11.2 | 1 / 18 | |
| 0.11.1 | 1 / 18 | |
| 0.11.0 | 1 / 18 | |
| 0.10.4 | 1 / 18 | |
| 0.10.3 | 1 / 18 | |
| 0.10.2 | 1 / 18 | |
| 0.10.1 | 1 / 18 | |
| 0.10.0 | 1 / 18 |
v0.34.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
2 findingsThis version was published by a different npm account than previous versions on 2026-07-20. 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.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.