@antelopejs/mongodb
MongoDB module that implements the Database interface of antelopejs
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@antelopejs/interface-mongodb | AI (dependencies): First-party interface package within the AntelopeJS ecosystem; expected dependency for this module. | ai | |
| dependencies | unvetted-dep:@antelopejs/interface-database | AI (dependencies): First-party interface package within the AntelopeJS ecosystem; expected dependency for this module. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is common (~88% of npm); no other risk signals present to amplify this. | ai | |
| phantom-deps | phantom-dep:chai | AI (phantom-deps): chai is declared as a runtime dep and used in test infrastructure; phantom-dep is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): reflect-metadata is a known implicit/side-effect import pattern in TypeScript decorator-based packages; stable false positive. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.2.1 | 8 / 13 | |
| 1.1.0 | 8 / 13 | |
| 1.0.8 | 8 / 13 | |
| 1.0.7 | 8 / 13 | |
| 1.0.6 | 8 / 13 | |
| 1.0.5 | 8 / 13 | |
| 1.0.4 | 8 / 13 | |
| 1.0.3 | 8 / 13 | |
| 1.0.2 | 8 / 13 | |
| 1.0.1 | 8 / 13 | |
| 1.0.0 | 8 / 13 | |
| 0.1.1 | 4 / 14 |
v1.2.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.