@microsoft/sp-odata-types
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): TypeScript helper library; implicit dependency pattern stable for this package. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): SWC helper library; implicit dependency pattern stable for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.23.2 | 2 / 3 | |
| 1.23.1 | 2 / 3 | |
| 1.23.0 | 2 / 3 | |
| 1.22.2 | 2 / 3 | |
| 1.22.1 | 2 / 3 | |
| 1.22.0 | 2 / 3 | |
| 1.21.1 | 2 / 3 | |
| 1.21.0 | 2 / 3 | |
| 1.20.0 | 1 / 3 | |
| 1.19.0 | 1 / 3 |
v1.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (microsoft1es) than the most recent previously approved version (odspnpm) on 2024-09-26, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.