b4a
Bridging the gap between buffers and typed arrays
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| — | typosquat.levenshtein:koa | — | sean |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.8.1 | 0 / 5 | |
| 1.8.0 | 0 / 4 | |
| 1.7.5 | 0 / 4 | |
| 1.7.4 | 0 / 4 | |
| 1.7.3 | 0 / 4 | |
| 1.7.2 | 0 / 4 | |
| 1.7.1 | 0 / 4 | |
| 1.7.0 | 0 / 4 | |
| 1.6.4 | 0 / 3 |
v1.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.