sop/jwx
The single-person project has no recent commit activity and no published release in nearly four years. Its license, repository tests, release notes, matching source repository, and lack of install scripts provide useful transparency, but the maintenance gap is substantial.
52%
Total Score
50
100
75
75
Health Score Breakdown
The latest release was published nearly four years ago, with no releases in the last 12 months; this materially raises abandonment risk despite a history of 18 releases.
Only one registry account has publishing access, leaving little visible publishing redundancy; the repository is user-owned, so no organizational backing offsets this concern.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the evidence of stalled maintenance.
Composer build tooling is present, but no security scanning tools were detected, leaving a useful but incomplete security-maintenance process.
The repository has no security policy, which is a meaningful transparency gap for a cryptographic JWT/JWS/JWE library.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Joni Eskelinen |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 sop/gcm Version ^3.0.0 | — | — |
sop/aes-kw Version ^3.0.0 | — | — |
sop/crypto-types Version ^0.3.0 | — | — |
sop/crypto-encoding Version ^0.3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 10 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.