← Home

@palantir/pack.state.foundry

npm Repository Homepage

PACK State service that integrates with Palantir Foundry platform APIs.

22
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

palantir

Keywords

pack

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Palantir org package transitioned to GitHub Actions publishing with SLSA attestation; expected CI/CD pattern. ai
provenance no-provenance AI (provenance): Established Palantir publisher; lack of Sigstore attestation is a process gap, not a security risk for this package. ai
phantom-deps phantom-dep:yjs AI (phantom-deps): Monorepo build artifact; declared dep used transitively, not a direct import. ai
phantom-deps phantom-dep:remeda AI (phantom-deps): Monorepo build artifact; declared dep used transitively, not a direct import. ai
phantom-deps phantom-dep:@osdk/api AI (phantom-deps): Monorepo build artifact; declared dep used transitively, not a direct import. ai
phantom-deps phantom-dep:conjure-client AI (phantom-deps): Monorepo build artifact; declared dep used transitively, not a direct import. ai

Versions (showing 22 of 22)

Version Deps Published
0.17.0 10 / 6
0.16.0 10 / 6
0.15.0 10 / 6
0.14.0 10 / 6
0.13.0 10 / 6
0.12.0 10 / 6
0.11.0 10 / 6
0.10.0 10 / 6
0.9.0 10 / 6
0.8.0 10 / 6
0.7.0 10 / 6
0.6.0 10 / 6
0.5.0 10 / 6
0.4.0 10 / 6
0.3.0 10 / 6
0.2.1 10 / 6
0.2.0 10 / 6
0.1.2 10 / 6
0.1.1 10 / 6
0.1.0 10 / 6
0.0.2 10 / 6
0.0.1 10 / 6

v0.17.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.16.0

2 findings
HIGH Publisher changed: palantir → GitHub Actions (on 2026-05-20) provenance

This 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.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.15.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.