The package is clearly licensed, actively released, and backed by a matching organization-owned repository with tests. Maintenance is concentrated in one contributor, while the repository has no security policy or scanning, leaving avoidable oversight gaps.
68%
Total Score
83
100
88
50
All four recent commits came from one contributor, creating a thin maintenance base; organization ownership offers some handoff capacity but no second active contributor is shown.
Composer build tooling is present, but no security-scanning tools were detected, reducing automated oversight of dependency and release risks.
The repository has no security policy, leaving users without documented vulnerability-reporting and response guidance.
Version 0.6.0 is not a stable major release, so compatibility expectations are lower, although it is not a prerelease and recent versions have been consistently published.
No GitHub Actions workflows were present, so there are no workflow findings or exposed workflow permissions; this also means no CI or automated release controls were observed.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
gpio/i2c Version ^0.6.0 | — | — |
gpio/spi Version ^0.6.0 | — | — |
gpio/digital Version ^0.6.0 | — | — |
gpio/contracts Version ^0.6.0 | — | — |
fabricate/circuits Version ^0.6.0 | — | — |
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.