@pi-r/atlas
MongoDB Atlas cloud functions for E-mc.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@e-mc/db | AI (dependencies): Same-author ecosystem dep, stable across versions. | ai | |
| dependencies | unvetted-dep:@e-mc/module | AI (dependencies): Same-author ecosystem dep, stable across versions. | ai | |
| dependencies | unvetted-dep:@e-mc/cloud | AI (dependencies): Same-author ecosystem dep, stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with consistent release history; lack of provenance is common and not a risk signal here. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 65-version history with consistent author/repo; long gap likely reflects development cycle, not takeover. | ai | |
| phantom-deps | phantom-dep:@e-mc/db | AI (phantom-deps): Analyzer notes it's referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@e-mc/module | AI (phantom-deps): Analyzer notes it's referenced in config files; stable false positive for this package. | ai |
Versions (showing 51 of 76)
| Version | Deps | Published |
|---|---|---|
| 0.12.3 | 6 / 0 | |
| 0.12.2 | 6 / 0 | |
| 0.12.1 | 6 / 0 | |
| 0.12.0 | 6 / 0 | |
| 0.11.3 | 6 / 0 | |
| 0.11.2 | 6 / 0 | |
| 0.11.1 | 6 / 0 | |
| 0.11.0 | 6 / 0 | |
| 0.10.5 | 6 / 0 | |
| 0.10.4 | 6 / 0 | |
| 0.10.3 | 6 / 0 | |
| 0.10.2 | 6 / 0 | |
| 0.10.1 | 6 / 0 | |
| 0.10.0 | 6 / 0 | |
| 0.9.6 | 6 / 0 | |
| 0.9.5 | 6 / 0 | |
| 0.9.4 | 6 / 0 | |
| 0.9.3 | 6 / 0 | |
| 0.9.2 | 6 / 0 | |
| 0.9.1 | 6 / 0 | |
| 0.9.0 | 6 / 0 | |
| 0.8.6 | 6 / 0 | |
| 0.8.5 | 6 / 0 | |
| 0.8.4 | 6 / 0 | |
| 0.8.3 | 6 / 0 | |
| 0.8.2 | 6 / 0 | |
| 0.8.1 | 6 / 0 | |
| 0.8.0 | 6 / 0 | |
| 0.7.7 | 6 / 0 | |
| 0.7.6 | 6 / 0 | |
| 0.7.5 | 6 / 0 | |
| 0.7.4 | 6 / 0 | |
| 0.7.3 | 6 / 0 | |
| 0.7.2 | 6 / 0 | |
| 0.7.1 | 6 / 0 | |
| 0.7.0 | 6 / 0 | |
| 0.6.11 | 6 / 0 | |
| 0.6.10 | 6 / 0 | |
| 0.6.9 | 6 / 0 | |
| 0.6.8 | 6 / 0 | |
| 0.6.7 | 6 / 0 | |
| 0.6.6 | 6 / 0 | |
| 0.6.5 | 6 / 0 | |
| 0.6.3 | 6 / 0 | |
| 0.6.2 | 6 / 0 | |
| 0.6.1 | 6 / 0 | |
| 0.6.0 | 6 / 0 | |
| 0.5.7 | 6 / 0 | |
| 0.5.6 | 6 / 0 | |
| 0.5.5 | 6 / 0 | |
| 0.5.4 | 6 / 0 |
v0.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.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.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.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.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.