disk
Pure-JS client and CLI for Archil disks
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Side effect of transition to CI/CD-attested publishing, not a compromise indicator. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Coincides with legitimate CI/CD provenance improvement, not account takeover. | ai | |
| dependencies | unvetted-dep:@archildata/api-types | AI (dependencies): First-party companion package matching Archil disk client scope. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): zod and archildata types are legitimate additions for this client library. | ai | |
| dependencies | unvetted-dep:openapi-fetch | AI (dependencies): openapi-fetch is a well-known, widely-used OpenAPI client library; its unvetted status is a pipeline artifact, not a real risk for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.8.22 | 5 / 4 | |
| 0.8.21 | 5 / 4 | |
| 0.8.20 | 5 / 4 | |
| 0.8.19 | 5 / 4 | |
| 0.8.18 | 3 / 5 | |
| 0.8.17 | 3 / 5 | |
| 0.8.16 | 3 / 5 | |
| 0.8.15 | 3 / 5 | |
| 0.8.14 | 3 / 5 | |
| 0.8.13 | 3 / 5 | |
| 0.8.12 | 2 / 4 | |
| 0.8.11 | 2 / 4 | |
| 0.8.10 | 2 / 4 | |
| 0.8.9 | 2 / 4 | |
| 0.8.8 | 2 / 4 | |
| 0.8.0 | 3 / 3 | |
| 0.7.1 | 3 / 3 | |
| 0.7.0 | 3 / 3 | |
| 0.6.2 | 3 / 3 | |
| 0.6.1 | 4 / 3 | |
| 0.6.0 | 4 / 3 | |
| 0.5.1 | 4 / 3 | |
| 0.5.0 | 4 / 3 | |
| 0.4.1 | 2 / 3 | |
| 0.4.0 | 2 / 1 | |
| 0.3.0 | 0 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v0.8.22
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published 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 (jhleath) on unknown date, 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.8.21
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jhleath.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.20
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jhleath.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.19
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jhleath.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
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.1
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.1
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.