@osdk/docs-spec-core
7
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
sauravsanjpalantirericanderson
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation from official Palantir repo; legitimate automation change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer added as part of Palantir org CI/CD transition; consistent with official repo ownership. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 0 / 2 | |
| 0.6.0 | 0 / 2 | |
| 0.5.0 | 0 / 2 | |
| 0.4.0 | 0 / 2 | |
| 0.3.0 | 0 / 2 | |
| 0.2.0 | 0 / 2 | |
| 0.1.0 | 0 / 2 |
v0.5.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.