@thi.ng/file-io
Assorted file I/O utils (w/ logging support) for NodeJS/Bun
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): thi.ng/umbrella does not use Sigstore provenance; consistent across all versions. | ai | |
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Sibling thi.ng/umbrella package; stable false positive for this monorepo. | ai | |
| dependencies | unvetted-dep:@thi.ng/hex | AI (dependencies): Sibling thi.ng/umbrella package; stable false positive for this monorepo. | ai | |
| dependencies | unvetted-dep:@thi.ng/random | AI (dependencies): Sibling thi.ng/umbrella package; stable false positive for this monorepo. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 5 / 4 | |
| 2.2.37 | 5 / 4 | |
| 2.2.36 | 5 / 4 | |
| 2.2.34 | 5 / 4 | |
| 2.2.33 | 5 / 4 | |
| 2.2.31 | 5 / 4 | |
| 2.2.30 | 5 / 4 | |
| 2.2.29 | 5 / 4 | |
| 2.2.28 | 5 / 4 | |
| 2.2.27 | 5 / 4 | |
| 2.2.26 | 5 / 4 | |
| 2.2.25 | 5 / 4 | |
| 2.2.24 | 5 / 4 | |
| 2.2.23 | 5 / 4 | |
| 2.2.22 | 5 / 4 | |
| 2.2.21 | 5 / 4 | |
| 2.2.20 | 5 / 4 | |
| 2.2.19 | 5 / 4 | |
| 2.2.18 | 5 / 4 | |
| 2.2.17 | 5 / 4 | |
| 2.2.16 | 5 / 4 | |
| 2.2.15 | 5 / 4 | |
| 2.2.11 | 5 / 4 | |
| 2.2.10 | 5 / 4 | |
| 2.2.9 | 5 / 4 | |
| 2.2.8 | 5 / 4 | |
| 2.2.7 | 5 / 4 | |
| 2.2.6 | 5 / 4 | |
| 2.2.5 | 5 / 4 | |
| 2.2.4 | 5 / 4 | |
| 2.2.3 | 5 / 4 | |
| 2.2.2 | 5 / 4 | |
| 2.2.1 | 5 / 4 | |
| 2.2.0 | 5 / 4 | |
| 2.1.38 | 5 / 4 | |
| 2.1.37 | 5 / 4 | |
| 2.1.36 | 5 / 4 |
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.