@arkstack/filesystem
Shared Filesystem utilities for ArkStack.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@aws-sdk/client-s3 | AI (phantom-deps): Framework-scoped AWS SDK dep loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/s3-request-presigner | AI (phantom-deps): Framework-scoped AWS SDK dep loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@arkstack/contract | AI (phantom-deps): Same-org scope package; likely re-exported or used indirectly within the monorepo. | ai |
Versions (showing 6 of 109)
| Version | Deps | Published |
|---|---|---|
| 0.3.1 | 7 / 1 | |
| 0.2.4 | 7 / 1 | |
| 0.2.3 | 7 / 1 | |
| 0.2.2 | 7 / 1 | |
| 0.2.1 | 7 / 1 | |
| 0.2.0 | 7 / 1 |
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.