@steedos/odata-v4-mongodb
Service OData requests from a MongoDB data store
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:odata-v4-literal | AI (dependencies): odata-v4-literal is a stable, narrow OData literal parser; constraint is pinned to ^0.1.0 with no known issues. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long history; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.0.14 | 2 / 0 | |
| 3.0.13 | 2 / 0 | |
| 3.0.12 | 2 / 0 | |
| 3.0.3 | 2 / 0 | |
| 3.0.0 | 2 / 0 | |
| 2.7.27 | 2 / 0 | |
| 2.7.25 | 2 / 0 | |
| 2.7.24 | 2 / 0 | |
| 2.7.23 | 2 / 0 |
v3.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.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.
v3.0.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.
v2.7.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.