sop/pkcs8
A single publisher and no security policy leave limited visible maintenance capacity. The source repository does contain tests, and the MIT license makes the package easier to evaluate and use.
43%
Total Score
25
75
50
Health Score Breakdown
The package has had no release in about seven years, with zero releases in the last 12 months; its four-release history shows limited ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and elevated abandonment risk.
One registry publisher provides little redundancy for maintaining or responding to issues, although the repository is not archived.
No security policy is present, leaving vulnerability reporting and response expectations undocumented for a cryptographic library.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Joni Eskelinen |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 sop/asn1 Version ^4.0.0 | — | — |
sop/pkcs5 Version ^0.3.0 | — | — |
sop/crypto-types Version ^0.3.0 | — | — |
sop/crypto-bridge Version ^0.3.1 | — | — |
sop/crypto-encoding Version ^0.3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 9 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.