mongodb-redact
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 | no-provenance | AI (provenance): Official MongoDB Inc package; lack of Sigstore provenance is acceptable for this established package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.4.12 | 2 / 17 | |
| 1.4.11 | 2 / 17 | |
| 1.4.10 | 2 / 17 | |
| 1.4.9 | 2 / 17 | |
| 1.4.8 | 2 / 17 | |
| 1.4.7 | 2 / 17 | |
| 1.4.6 | 2 / 17 | |
| 1.4.5 | 2 / 17 | |
| 1.4.4 | 2 / 17 | |
| 1.4.3 | 2 / 17 | |
| 1.4.0 | 2 / 17 | |
| 1.3.0 | 2 / 17 | |
| 1.2.2 | 1 / 17 | |
| 1.2.1 | 1 / 17 | |
| 1.2.0 | 1 / 17 | |
| 1.1.8 | 0 / 16 | |
| 1.1.7 | 0 / 16 | |
| 1.1.6 | 0 / 16 | |
| 1.1.5 | 0 / 16 | |
| 1.1.4 | 1 / 16 | |
| 1.1.3 | 1 / 16 | |
| 1.1.2 | 1 / 16 | |
| 1.1.1 | 1 / 16 | |
| 1.1.0 | 1 / 16 |
v1.4.12
2 findingsThis version was published by a different npm account than previous versions on unknown date. 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.
v1.4.9
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.