@osdk/react-components
> **⚠️ Beta Release**: This package is currently in beta. Please use the latest beta version for the most up-to-date features and fixes.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Palantir org package; new maintainer has palantir-suffixed username consistent with internal team growth. | ai | |
| dependencies | unvetted-dep:xlsx | AI (dependencies): xlsx is used for the experimental excel-viewer component; consistent with package purpose across versions. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): date-fns is a transitive peer of react-day-picker; phantom-dep heuristic fires as false positive here. | ai | |
| provenance | publisher-changed | AI (provenance): Palantir migrated publishing to GitHub Actions CI with SLSA attestation; stable pattern for this org. | ai | |
| phantom-deps | phantom-dep:date-fns-tz | AI (phantom-deps): Same as date-fns; used transitively via react-day-picker ecosystem. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Palantir OSDK component library; large file additions reflect legitimate feature expansion, not injected code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase matches 7 new well-known runtime deps added in this version. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Palantir OSDK monorepo uses 0.0.0 as a placeholder version; not a malware signal for this publisher. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.27.0 | 19 / 16 | |
| 0.26.0 | 19 / 16 | |
| 0.22.0 | 19 / 17 | |
| 0.21.0 | 19 / 17 | |
| 0.20.0 | 19 / 17 | |
| 0.19.0 | 19 / 17 | |
| 0.16.0 | 20 / 17 | |
| 0.15.0 | 17 / 17 | |
| 0.13.0 | 17 / 16 | |
| 0.12.0 | 16 / 16 | |
| 0.11.0 | 16 / 16 | |
| 0.10.0 | 16 / 16 | |
| 0.9.0 | 16 / 16 | |
| 0.8.0 | 16 / 16 | |
| 0.7.0 | 16 / 16 | |
| 0.6.0 | 16 / 16 | |
| 0.5.0 | 16 / 16 | |
| 0.4.0 | 16 / 16 | |
| 0.3.0 | 11 / 15 | |
| 0.2.0 | 11 / 15 | |
| 0.1.0 | 4 / 12 | |
| 0.0.0 | 0 / 8 |
v0.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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
2 findingsThis version was published by a different npm account than previous versions on 2026-04-23. 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.
v0.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-22. 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.
v0.5.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.
v0.4.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.
v0.3.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.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.