The MIT license, clear README, and small runtime dependency set support straightforward adoption. Security guidance is absent, and all recent repository work comes from one contributor, which raises continuity concerns.
72%
Total Score
67
100
93
50
One registry maintainer is consistent with the repository being owned by an individual, but it leaves little publishing redundancy.
All seven recent commits came from one contributor, so maintenance depends entirely on a single active developer and has limited handoff resilience.
Composer build tooling is present, but no security-scanning tooling was detected for a cryptographic signing library, leaving a meaningful review gap.
The repository has no security policy, making it unclear how vulnerability reports are handled for a library that processes certificates and private keys.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
sop/asn1 Version ~4.1.1 | — | — |
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.