← Home

@palantir/pack.state.foundry-event

PACK event service for real-time document synchronization

21
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
dependencies unvetted-dep:@palantir/pack.auth AI (dependencies): First-party Palantir sibling package; stable false positive for this org's packages. ai
dependencies unvetted-dep:@palantir/pack.core AI (dependencies): First-party Palantir sibling package; stable false positive for this org's packages. ai
dependencies unvetted-dep:@osdk/foundry.pack AI (dependencies): Palantir OSDK package; expected dependency for Palantir ecosystem tooling. ai
provenance no-provenance AI (provenance): Palantir publishes many packages without Sigstore provenance; consistent across their portfolio. ai

Versions (showing 21 of 21)

Version Deps Published
0.22.0 8 / 7
0.21.0 8 / 7
0.14.0 8 / 7
0.13.0 8 / 7
0.12.0 8 / 7
0.11.0 8 / 7
0.10.0 9 / 6
0.9.0 9 / 6
0.8.0 9 / 6
0.7.0 9 / 6
0.6.0 9 / 6
0.5.0 9 / 6
0.4.0 9 / 6
0.3.0 9 / 6
0.2.1 9 / 6
0.2.0 9 / 6
0.1.2 9 / 6
0.1.1 9 / 6
0.1.0 9 / 6
0.0.2 9 / 6
0.0.1 9 / 6

v0.22.0

2 findings
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.

INFO Publisher changed: palantir → GitHub Actions (on 2026-07-16, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (palantir) on 2026-07-16, 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.21.0

2 findings
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.

INFO Publisher changed: palantir → GitHub Actions (on 2026-07-10, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (palantir) on 2026-07-10, 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.