bare-rpc
librpc ABI compatible RPC for Bare
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 |
|---|---|---|---|---|
| dependencies | unvetted-peer-dep:bare-buffer | AI (dependencies): Optional peer dependency; stable across versions. | ai | |
| dependencies | unvetted-dep:b4a | AI (dependencies): b4a is a standard Holepunch buffer utility; stable false positive for this package family. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.3.2 | 4 / 6 | |
| 1.3.1 | 4 / 6 | |
| 1.3.0 | 4 / 6 | |
| 1.2.0 | 4 / 5 | |
| 1.1.0 | 4 / 5 | |
| 1.0.0 | 4 / 5 |
v1.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.