@osdk/internal.foundry.core
This is an internal only package.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@osdk/shared.client | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo type-only or re-export packages. | ai | |
| phantom-deps | phantom-dep:@osdk/shared.client2 | AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@osdk/shared.net.platformapi | AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal SDK package from Palantir monorepo; sparse README and no keywords are expected for internal/generated packages. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 2.59.0 | 4 / 2 | |
| 2.58.0 | 4 / 2 | |
| 2.57.0 | 4 / 2 | |
| 2.45.0 | 4 / 2 | |
| 2.44.0 | 4 / 2 | |
| 2.43.0 | 4 / 2 | |
| 2.42.0 | 4 / 2 | |
| 2.41.0 | 4 / 2 | |
| 2.40.0 | 4 / 2 | |
| 2.39.0 | 4 / 2 | |
| 2.38.0 | 4 / 2 | |
| 2.37.0 | 4 / 2 | |
| 2.36.0 | 4 / 2 | |
| 2.35.0 | 4 / 2 | |
| 2.34.0 | 4 / 2 | |
| 2.33.0 | 4 / 2 | |
| 2.32.0 | 4 / 2 | |
| 2.31.0 | 4 / 2 | |
| 2.30.0 | 4 / 2 | |
| 2.29.0 | 4 / 2 | |
| 2.28.0 | 4 / 2 | |
| 2.27.0 | 4 / 2 | |
| 2.26.0 | 4 / 2 | |
| 2.25.0 | 4 / 2 | |
| 2.24.0 | 4 / 2 | |
| 2.23.0 | 4 / 2 | |
| 2.22.0 | 4 / 2 | |
| 2.21.0 | 4 / 2 | |
| 2.20.0 | 4 / 2 | |
| 0.1.4 | 4 / 4 |
v2.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sauravsanj) than the most recent previously approved version (palantir) on 2026-04-13, but sauravsanj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.