@osdk/maker
The Maker package provides a type-safe, programmatic way to define ontologies, which are the foundation for structured data in Palantir Foundry. This document provides examples of how to use the maker API to define various ontology entities.
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/gateway | AI (dependencies): First-party @osdk sibling package from same Palantir monorepo. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @osdk package, low risk. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Common across this monorepo's packages, not a spam signal. | ai | |
| phantom-deps | phantom-dep:jiti | AI (phantom-deps): jiti is a declared runtime dep used as a config loader; phantom-dep heuristic fires on indirect usage patterns common in CLI tools. | ai | |
| phantom-deps | phantom-dep:semver-ts | AI (phantom-deps): Declared runtime dep; phantom-dep firing on config-file references is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): ts-node declared as runtime dep for TypeScript execution; referenced in config files is expected for this CLI tool. | ai | |
| phantom-deps | phantom-dep:@osdk/api | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive for monorepo packages. | ai |
Versions (showing 64 of 64)
| Version | Deps | Published |
|---|---|---|
| 0.51.0 | 10 / 8 | |
| 0.50.0 | 10 / 8 | |
| 0.49.0 | 10 / 8 | |
| 0.48.0 | 10 / 8 | |
| 0.47.0 | 10 / 8 | |
| 0.46.0 | 10 / 8 | |
| 0.45.0 | 10 / 8 | |
| 0.44.0 | 10 / 8 | |
| 0.43.0 | 10 / 8 | |
| 0.42.0 | 10 / 8 | |
| 0.41.0 | 10 / 8 | |
| 0.40.0 | 10 / 8 | |
| 0.39.0 | 10 / 8 | |
| 0.38.0 | 10 / 8 | |
| 0.37.0 | 10 / 8 | |
| 0.36.0 | 10 / 8 | |
| 0.35.0 | 10 / 8 | |
| 0.34.0 | 10 / 8 | |
| 0.33.0 | 10 / 8 | |
| 0.32.0 | 10 / 8 | |
| 0.31.0 | 10 / 8 | |
| 0.30.0 | 10 / 8 | |
| 0.29.0 | 10 / 8 | |
| 0.28.0 | 10 / 8 | |
| 0.27.0 | 10 / 8 | |
| 0.26.0 | 10 / 8 | |
| 0.25.0 | 10 / 8 | |
| 0.24.0 | 10 / 8 | |
| 0.23.0 | 10 / 8 | |
| 0.22.0 | 10 / 8 | |
| 0.21.0 | 10 / 8 | |
| 0.20.0 | 10 / 8 | |
| 0.19.0 | 10 / 8 | |
| 0.18.0 | 10 / 8 | |
| 0.17.0 | 10 / 8 | |
| 0.16.0 | 10 / 8 | |
| 0.13.0 | 8 / 7 | |
| 0.12.2 | 7 / 8 | |
| 0.12.1 | 7 / 8 | |
| 0.12.0 | 7 / 8 | |
| 0.11.4 | 7 / 8 | |
| 0.11.3 | 7 / 8 | |
| 0.11.2 | 7 / 8 | |
| 0.11.1 | 7 / 8 | |
| 0.11.0 | 7 / 8 | |
| 0.10.1 | 6 / 8 | |
| 0.10.0 | 6 / 8 | |
| 0.9.5 | 6 / 7 | |
| 0.8.13 | 6 / 8 | |
| 0.8.12 | 6 / 8 | |
| 0.8.11 | 6 / 8 | |
| 0.8.10 | 6 / 8 | |
| 0.8.9 | 6 / 8 | |
| 0.8.8 | 6 / 8 | |
| 0.8.7 | 6 / 8 | |
| 0.8.6 | 6 / 8 | |
| 0.8.5 | 6 / 8 | |
| 0.8.4 | 6 / 8 | |
| 0.8.3 | 6 / 8 | |
| 0.8.2 | 6 / 8 | |
| 0.8.1 | 6 / 8 | |
| 0.8.0 | 6 / 8 | |
| 0.7.2 | 7 / 7 | |
| 0.7.0 | 7 / 7 |
v0.51.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.50.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.49.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.48.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.47.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.46.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.45.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.44.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.18.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (palantir) on 2026-04-21, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.17.0
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.
v0.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.