@palantir/pack.document-schema.type-gen
TypeScript type generation from document schema
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Palantir org migrated publishing to GitHub Actions CI/CD; confirmed by SLSA provenance attestation from official repo. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a sibling Palantir scoped package; low risk for this publisher. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Minor version bump from 0.0.4 to 0.1.0 for a type-gen tool; file growth is expected and no malicious patterns detected. | ai | |
| phantom-deps | phantom-dep:bun | AI (phantom-deps): bun is listed as a runtime dep and used as a CLI binary target; phantom-dep false positive for this package. | ai | |
| npm-metadata | url-dep:@palantir/pack-docschema-api | AI (npm-metadata): File: dep is a monorepo bundling pattern for Palantir's internal library; stable across versions. | ai | |
| phantom-deps | phantom-dep:conjure-client | AI (phantom-deps): conjure-client is referenced in config files per the finding; stable false positive for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.13.0 | 12 / 8 | |
| 0.12.0 | 12 / 8 | |
| 0.11.0 | 12 / 8 | |
| 0.10.0 | 12 / 8 | |
| 0.9.0 | 12 / 8 | |
| 0.8.0 | 12 / 8 | |
| 0.7.0 | 12 / 8 | |
| 0.6.0 | 12 / 8 | |
| 0.5.0 | 12 / 8 | |
| 0.4.0 | 12 / 8 | |
| 0.3.0 | 12 / 8 | |
| 0.2.2 | 12 / 8 | |
| 0.2.1 | 12 / 8 | |
| 0.2.0 | 12 / 8 | |
| 0.1.1 | 12 / 8 | |
| 0.1.0 | 12 / 8 | |
| 0.0.4 | 12 / 8 | |
| 0.0.3 | 12 / 8 | |
| 0.0.2 | 12 / 8 | |
| 0.0.1 | 13 / 8 |
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
2 findingsThis version was published by a different npm account than previous versions on 2026-05-20. 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.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.