@classytic/mongokit
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Shift to org's own bot publisher with strong track record, not third-party takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same bot-account transition, consistent with CI automation rollout. | ai |
Versions (showing 51 of 77)
| Version | Deps | Published |
|---|---|---|
| 3.28.0 | 0 / 20 | |
| 3.25.0 | 0 / 20 | |
| 3.24.0 | 0 / 20 | |
| 3.23.0 | 0 / 20 | |
| 3.22.2 | 0 / 20 | |
| 3.22.1 | 0 / 20 | |
| 3.22.0 | 0 / 20 | |
| 3.21.0 | 0 / 20 | |
| 3.20.0 | 0 / 20 | |
| 3.19.0 | 0 / 20 | |
| 3.18.0 | 0 / 20 | |
| 3.17.0 | 0 / 19 | |
| 3.16.2 | 0 / 19 | |
| 3.16.1 | 0 / 19 | |
| 3.16.0 | 0 / 19 | |
| 3.15.0 | 0 / 19 | |
| 3.14.0 | 0 / 19 | |
| 3.13.4 | 0 / 19 | |
| 3.13.3 | 0 / 19 | |
| 3.13.2 | 0 / 19 | |
| 3.13.1 | 0 / 19 | |
| 3.13.0 | 0 / 19 | |
| 3.12.0 | 0 / 16 | |
| 3.11.1 | 0 / 15 | |
| 3.11.0 | 0 / 15 | |
| 3.10.3 | 0 / 15 | |
| 3.10.2 | 0 / 15 | |
| 3.10.1 | 0 / 15 | |
| 3.10.0 | 0 / 15 | |
| 3.8.0 | 0 / 14 | |
| 3.7.0 | 0 / 14 | |
| 3.6.4 | 0 / 13 | |
| 3.6.3 | 0 / 13 | |
| 3.6.2 | 0 / 11 | |
| 3.6.1 | 0 / 9 | |
| 3.6.0 | 0 / 9 | |
| 3.5.6 | 0 / 9 | |
| 3.5.5 | 0 / 9 | |
| 3.5.4 | 0 / 9 | |
| 3.5.3 | 0 / 9 | |
| 3.5.2 | 0 / 9 | |
| 3.5.1 | 0 / 9 | |
| 3.5.0 | 0 / 9 | |
| 3.4.5 | 0 / 8 | |
| 3.4.4 | 0 / 8 | |
| 3.4.3 | 0 / 8 | |
| 3.4.2 | 0 / 8 | |
| 3.4.1 | 0 / 8 | |
| 3.4.0 | 0 / 8 | |
| 3.3.2 | 0 / 7 | |
| 3.3.1 | 0 / 7 |
v3.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-07. 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.
v3.18.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-04. 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.
v3.17.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-28. 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.
v3.16.2
2 findingsThis version was published by a different npm account than previous versions on 2026-06-27. 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.
v3.16.1
2 findingsThis version was published by a different npm account than previous versions on 2026-06-18. 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.