@osdk/client
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@osdk/foundry.functions | AI (dependencies): Same-org Palantir OSDK sibling package, consistent with existing @osdk/foundry.* deps pattern. | ai | |
| provenance | publisher-changed | AI (provenance): Palantir org uses GitHub Actions for automated publishing; CI publisher is expected for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Palantir org maintainer addition consistent with team growth; SLSA provenance confirms CI-controlled release. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New internal-node entry point added; large file count is expected for a bundled CJS build. | ai | |
| source-diff | obfuscated-file:build/cjs/public/internal-node.cjs | AI (source-diff): Standard CJS bundle output from Palantir monorepo transpile step; long lines are minified but not obfuscated. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by new internal-node bundle; consistent with monorepo release pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @osdk/foundry.mediasets is a sibling Palantir package at matching version 2.44.0; expected coordinated release. | ai | |
| phantom-deps | phantom-dep:fast-deep-equal | AI (phantom-deps): Same monorepo pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:fetch-retry | AI (phantom-deps): Palantir OSDK monorepo pattern; declared in package.json but resolved transitively — stable false positive. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Palantir monorepo package; empty description is a consistent pattern across all @osdk/* packages. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): Type-only dep used for GeoJSON typings; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a declared runtime dep used via isomorphic-ws; phantom-dep heuristic fires incorrectly here. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 2.30.0 | 22 / 21 | |
| 2.29.0 | 22 / 21 | |
| 2.28.0 | 22 / 21 | |
| 2.27.0 | 22 / 21 | |
| 2.26.0 | 22 / 21 | |
| 2.25.0 | 22 / 21 | |
| 2.24.0 | 22 / 21 | |
| 2.23.0 | 22 / 21 | |
| 2.22.0 | 22 / 21 | |
| 2.21.0 | 22 / 21 | |
| 2.20.0 | 22 / 21 | |
| 2.19.0 | 21 / 21 | |
| 2.17.0 | 21 / 21 | |
| 2.16.0 | 21 / 21 | |
| 2.15.0 | 21 / 21 | |
| 2.14.0 | 21 / 21 | |
| 2.13.0 | 21 / 21 | |
| 2.12.0 | 21 / 21 | |
| 2.11.0 | 21 / 21 | |
| 2.10.0 | 21 / 20 | |
| 2.9.0 | 21 / 22 | |
| 2.8.0 | 21 / 22 | |
| 2.7.8 | 25 / 21 | |
| 2.4.2 | 24 / 22 | |
| 2.4.1 | 24 / 22 | |
| 2.4.0 | 24 / 22 | |
| 2.3.4 | 24 / 22 | |
| 2.3.3 | 24 / 22 | |
| 2.3.2 | 24 / 22 | |
| 2.3.1 | 24 / 22 | |
| 2.3.0 | 24 / 22 | |
| 2.2.1 | 24 / 22 | |
| 2.2.0 | 24 / 22 | |
| 2.1.5 | 22 / 20 | |
| 0.21.4 | 17 / 19 |
v2.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.8
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.