@osdk/docs-spec-sdk
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Palantir @osdk monorepo uses 0.0.0 as a stable placeholder version across multiple packages; not a malware indicator here. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from individual (ericanderson) to org account (palantir) matches official repo ownership; stable for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal Palantir SDK spec package; missing description is cosmetic, not a malice indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established Palantir publisher; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 1 / 2 | |
| 0.17.0 | 1 / 2 | |
| 0.16.0 | 1 / 2 | |
| 0.15.0 | 1 / 2 | |
| 0.14.0 | 1 / 2 | |
| 0.13.0 | 1 / 2 | |
| 0.12.0 | 1 / 2 | |
| 0.11.0 | 1 / 2 | |
| 0.10.0 | 1 / 2 | |
| 0.9.0 | 1 / 2 | |
| 0.8.0 | 1 / 2 | |
| 0.7.0 | 1 / 2 | |
| 0.6.0 | 1 / 2 | |
| 0.5.0 | 1 / 2 | |
| 0.4.0 | 1 / 2 | |
| 0.3.0 | 1 / 2 | |
| 0.2.0 | 1 / 2 | |
| 0.1.0 | 1 / 2 | |
| 0.0.0 | 1 / 2 |
v0.18.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.
v0.16.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.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.13.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.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
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.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.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.