@mongosh/history
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): mcasimir_mdb appears to be a renamed/updated account for the same MongoDB contributor within the mongosh org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): mcasimir removal paired with mcasimir_mdb addition indicates account rename, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Active mongosh monorepo package; dormancy signal is a false positive for this sub-package with 135 published versions. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 2.4.13 | 1 / 5 | |
| 2.4.12 | 1 / 6 | |
| 2.4.11 | 1 / 6 | |
| 2.4.9 | 2 / 7 | |
| 2.4.8 | 2 / 7 | |
| 2.4.6 | 2 / 7 | |
| 2.4.5 | 2 / 7 | |
| 2.4.4 | 2 / 7 | |
| 2.4.2 | 2 / 7 | |
| 2.4.0 | 2 / 7 | |
| 2.3.8 | 2 / 7 | |
| 2.3.7 | 2 / 7 | |
| 2.3.6 | 2 / 7 | |
| 2.3.5 | 2 / 7 | |
| 2.3.4 | 2 / 7 | |
| 2.3.3 | 2 / 7 | |
| 2.3.2 | 2 / 7 | |
| 2.3.1 | 2 / 7 | |
| 2.3.0 | 2 / 7 | |
| 2.2.15 | 2 / 7 | |
| 2.2.12 | 2 / 7 | |
| 2.2.11 | 2 / 7 | |
| 2.2.10 | 2 / 8 | |
| 2.2.9 | 2 / 8 | |
| 2.2.6 | 2 / 8 |
v2.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.