@thi.ng/block-fs
Customizable block-based storage, adapters & file system layer
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Sibling package from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/args | AI (dependencies): Sibling package from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/mime | AI (dependencies): Sibling package from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/binary | AI (dependencies): Sibling package from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/random | AI (dependencies): Sibling package from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/compare | AI (dependencies): Sibling package from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/file-io | AI (dependencies): Sibling package from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/strings | AI (dependencies): Sibling package from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/bitfield | AI (dependencies): Sibling package from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): thi.ng/umbrella does not publish with Sigstore provenance; consistent across all versions. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 0.6.55 | 12 / 4 | |
| 0.6.54 | 12 / 4 | |
| 0.6.53 | 12 / 4 | |
| 0.6.51 | 12 / 4 | |
| 0.6.50 | 12 / 4 | |
| 0.6.48 | 12 / 4 | |
| 0.6.47 | 12 / 4 | |
| 0.6.46 | 12 / 4 | |
| 0.6.45 | 12 / 4 | |
| 0.6.44 | 12 / 4 | |
| 0.6.43 | 12 / 4 | |
| 0.6.42 | 12 / 4 | |
| 0.6.41 | 12 / 4 | |
| 0.6.40 | 12 / 4 | |
| 0.6.39 | 12 / 4 | |
| 0.6.37 | 12 / 4 | |
| 0.6.36 | 12 / 4 | |
| 0.6.35 | 12 / 4 | |
| 0.6.34 | 12 / 4 | |
| 0.6.33 | 12 / 4 | |
| 0.6.32 | 12 / 4 | |
| 0.6.31 | 12 / 4 | |
| 0.6.29 | 12 / 4 | |
| 0.6.28 | 12 / 4 | |
| 0.6.27 | 12 / 4 | |
| 0.6.26 | 12 / 4 | |
| 0.6.25 | 12 / 4 | |
| 0.6.24 | 12 / 4 | |
| 0.6.20 | 12 / 4 | |
| 0.6.19 | 12 / 4 | |
| 0.6.18 | 12 / 4 | |
| 0.6.17 | 12 / 4 | |
| 0.6.16 | 12 / 4 | |
| 0.6.15 | 12 / 4 | |
| 0.6.14 | 12 / 4 | |
| 0.6.13 | 12 / 4 | |
| 0.6.12 | 12 / 4 | |
| 0.6.11 | 12 / 4 | |
| 0.6.10 | 12 / 4 | |
| 0.6.8 | 12 / 4 | |
| 0.6.7 | 12 / 4 | |
| 0.6.6 | 12 / 4 | |
| 0.6.5 | 12 / 4 | |
| 0.6.4 | 12 / 4 | |
| 0.6.3 | 12 / 4 | |
| 0.6.2 | 12 / 4 | |
| 0.6.1 | 12 / 4 | |
| 0.6.0 | 11 / 4 | |
| 0.5.10 | 11 / 4 | |
| 0.5.9 | 11 / 4 | |
| 0.5.8 | 11 / 4 |
v0.6.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.27
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.26
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.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.