@osdk/typescript-sdk-docs
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 monorepo doc package; 0.0.0 is intentional versioning, not a throwaway. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal docs package in a large monorepo; missing description is benign here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.13.0 | 3 / 4 | |
| 0.12.0 | 3 / 4 | |
| 0.11.0 | 3 / 4 | |
| 0.10.0 | 3 / 4 | |
| 0.9.0 | 3 / 4 | |
| 0.8.0 | 3 / 4 | |
| 0.7.0 | 3 / 4 | |
| 0.6.0 | 3 / 4 | |
| 0.5.0 | 3 / 4 | |
| 0.4.0 | 3 / 4 | |
| 0.3.0 | 3 / 4 | |
| 0.2.0 | 3 / 4 | |
| 0.1.0 | 3 / 4 | |
| 0.0.0 | 3 / 4 |
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.