@mongodb-js/mongodb-downloader
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): mcasimir_mdb is a rename of mcasimir within the MongoDB org; not a third-party takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of mcasimir paired with addition of mcasimir_mdb indicates a username change, not a hostile removal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate MongoDB tooling package in the mongodb-js org; templated naming is intentional for the monorepo. | ai | |
| provenance | no-provenance | AI (provenance): MongoDB-js org package; provenance absence is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.14 | 6 / 22 | |
| 1.1.13 | 6 / 22 | |
| 1.1.12 | 6 / 22 | |
| 1.1.11 | 6 / 22 | |
| 1.1.10 | 6 / 22 | |
| 1.1.9 | 6 / 22 | |
| 1.1.8 | 6 / 22 | |
| 1.1.7 | 6 / 22 | |
| 1.1.6 | 6 / 22 | |
| 1.1.5 | 6 / 22 | |
| 1.1.4 | 6 / 22 | |
| 1.1.3 | 6 / 22 | |
| 1.1.0 | 6 / 22 | |
| 1.0.0 | 6 / 22 |
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.
v1.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.