@stacksjs/storage
The Stacks file system.
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Stacksjs monorepo publishes many packages together via CI; normal cadence. | ai | |
| dependencies | unvetted-dep:ts-images | AI (dependencies): New but narrowly-scoped dep, no fetch/exec behavior; consistent with package's file/storage purpose. | ai | |
| phantom-deps | phantom-dep:@stacksjs/path | AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@stacksjs/arrays | AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@stacksjs/strings | AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/archiver | AI (phantom-deps): Type definitions for archiver; used in build/types generation. | ai | |
| phantom-deps | phantom-dep:archiver | AI (phantom-deps): Archiver is used in dist build; phantom-dep heuristic misses transitive/build-time usage. | ai | |
| provenance | publisher-changed | AI (provenance): Manual-to-CI/CD provenance transition, not an account compromise indicator. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo lockstep versioning explains dormancy; no diff/behavior change. | ai |
Versions (showing 38 of 154)
| Version | Deps | Published |
|---|---|---|
| 0.70.61 | 1 / 6 | |
| 0.70.60 | 1 / 6 | |
| 0.70.59 | 1 / 6 | |
| 0.70.58 | 1 / 6 | |
| 0.70.57 | 1 / 6 | |
| 0.70.56 | 1 / 6 | |
| 0.70.55 | 1 / 6 | |
| 0.70.54 | 1 / 6 | |
| 0.70.53 | 1 / 6 | |
| 0.70.45 | 1 / 6 | |
| 0.70.44 | 1 / 6 | |
| 0.70.43 | 1 / 6 | |
| 0.70.42 | 1 / 6 | |
| 0.70.37 | 1 / 6 | |
| 0.70.36 | 1 / 6 | |
| 0.70.35 | 1 / 6 | |
| 0.70.34 | 1 / 6 | |
| 0.70.33 | 1 / 6 | |
| 0.70.32 | 1 / 6 | |
| 0.70.31 | 1 / 6 | |
| 0.70.30 | 1 / 6 | |
| 0.70.29 | 1 / 6 | |
| 0.70.28 | 1 / 6 | |
| 0.70.27 | 1 / 6 | |
| 0.70.26 | 1 / 6 | |
| 0.70.25 | 1 / 6 | |
| 0.67.0 | 9 / 7 | |
| 0.65.0 | 0 / 0 | |
| 0.64.6 | 10 / 1 | |
| 0.64.5 | 10 / 1 | |
| 0.64.4 | 10 / 1 | |
| 0.64.3 | 10 / 1 | |
| 0.64.2 | 10 / 1 | |
| 0.64.1 | 10 / 1 | |
| 0.64.0 | 10 / 1 | |
| 0.63.1 | 10 / 1 | |
| 0.63.0 | 10 / 1 | |
| 0.62.0 | 10 / 1 |
v0.70.61
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.60
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.59
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.58
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.57
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.56
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.55
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.54
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.53
2 findingsThis version was published by a different npm account than previous versions on 2026-07-10. 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.70.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.