Clear documentation, bundled typings, and a tested source tree make integration straightforward. Read-only workflow permissions and npm provenance are reassuring, though action references are not pinned.
88%
Total Score
100
100
94
75
100
The project uses CMake for its native build, but no security scanning tools were detected. The missing scanner is a modest transparency gap, not evidence of unsafe maintenance by itself.
The repository has no published security policy. This weakens vulnerability-reporting transparency, though it is partly offset by the project's active maintenance and organization ownership.
All three workflows use read-only permissions and contain no high- or medium-confidence audit findings, but all 12 action references are unpinned. That leaves avoidable build-reproducibility and action-supply-chain exposure.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
bare-url Version ^2.2.2 | — | — |
bare-path Version ^3.0.0 | — | — |
fast-fifo Version ^1.3.2 | — | — |
bare-events Version ^2.5.4 | — | — |
bare-stream Version ^2.6.4 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.