mhujer/jms-serializer-uuid
Clear documentation, tests, and a small dependency set make integration straightforward. The single-person project has no security scanning, and its workflow uses unpinned actions, increasing maintenance and build hygiene concerns.
52%
Total Score
50
100
88
83
Health Score Breakdown
One registry publisher is normal for a user-owned project, but it provides limited visible succession capacity when combined with no recent commits.
The latest release was in December 2021, nearly five years ago, with no releases in the last 12 months. Its nine-release history shows a long-lived package but not current maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe defect.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but all three action references are unpinned. That leaves build inputs less reproducible and more exposed to upstream changes.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Martin Hujer |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 ramsey/uuid Version ~3.0|~4.0 | — | — |
jms/serializer Version ~3.14 | — | — |
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.