@palantir/pack.state.core
PACK State logic and utilities
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@palantir/pack.core | AI (dependencies): Sibling package from the same Palantir monorepo; expected intra-org dependency. | ai | |
| provenance | no-provenance | AI (provenance): Palantir org package; no provenance is consistent across their published packages and not a risk signal here. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 6 / 6 | |
| 0.11.0 | 6 / 6 | |
| 0.10.0 | 6 / 6 | |
| 0.9.0 | 6 / 6 | |
| 0.8.0 | 6 / 6 | |
| 0.7.0 | 6 / 6 | |
| 0.6.0 | 6 / 6 | |
| 0.5.0 | 6 / 6 | |
| 0.4.0 | 6 / 6 | |
| 0.3.1 | 6 / 6 | |
| 0.3.0 | 6 / 6 | |
| 0.2.2 | 6 / 6 | |
| 0.2.1 | 6 / 6 | |
| 0.2.0 | 6 / 6 | |
| 0.1.1 | 6 / 6 | |
| 0.1.0 | 6 / 6 |
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.