@kb-labs/adapters-fs
Filesystem adapter implementing IStorage interface
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with clean history; lack of Sigstore attestation is a process gap, not a security risk. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 2.104.0 | 2 / 9 | |
| 2.103.0 | 2 / 9 | |
| 2.102.0 | 2 / 9 | |
| 2.101.0 | 2 / 9 | |
| 2.100.0 | 2 / 9 | |
| 2.98.0 | 2 / 9 | |
| 2.96.0 | 2 / 9 | |
| 2.94.0 | 2 / 9 | |
| 2.93.0 | 2 / 9 | |
| 2.89.0 | 2 / 9 | |
| 2.88.0 | 2 / 9 | |
| 2.82.0 | 2 / 9 | |
| 2.76.0 | 2 / 9 | |
| 2.73.0 | 2 / 9 | |
| 2.67.0 | 2 / 9 | |
| 2.66.0 | 2 / 9 | |
| 2.64.0 | 2 / 9 | |
| 2.63.0 | 2 / 9 | |
| 2.54.0 | 2 / 9 | |
| 2.46.0 | 2 / 9 | |
| 2.45.0 | 2 / 9 | |
| 2.42.0 | 2 / 9 | |
| 2.39.0 | 2 / 9 | |
| 2.32.0 | 2 / 9 | |
| 2.29.0 | 2 / 9 | |
| 2.25.0 | 2 / 9 | |
| 2.23.0 | 2 / 9 | |
| 2.19.0 | 2 / 9 | |
| 2.18.0 | 2 / 9 | |
| 2.17.0 | 2 / 9 | |
| 2.16.0 | 2 / 9 | |
| 2.13.0 | 2 / 9 | |
| 2.12.0 | 2 / 9 | |
| 2.9.0 | 2 / 9 | |
| 2.6.0 | 2 / 9 | |
| 0.8.0 | 2 / 9 | |
| 0.7.0 | 2 / 9 | |
| 0.6.0 | 2 / 9 | |
| 0.5.0 | 2 / 9 | |
| 0.4.0 | 2 / 9 | |
| 0.3.0 | 2 / 9 | |
| 0.2.0 | 2 / 9 |
v2.104.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.103.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.102.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.101.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.100.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.96.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.