The package is clearly documented and licensed, with recent release notes and repository tests. Maintenance is active, but one contributor carries all recent commits and workflow checks include high-confidence template-injection risk with every action unpinned.
67%
Total Score
67
100
100
50
The registry namespace and repository are owned by the same individual, so the package identity is clear, but there is no organization backing to offset the concentrated contributor base.
All eight commits in the last three months came from one contributor, giving the project a single-person maintenance dependency and increasing continuity risk.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented for consumers.
All eight analyzed action references are unpinned, and the audit found a high-confidence template-injection issue in autoapprove.yaml; the workflow also has top-level write permissions. These are workflow hygiene and supply-chain concerns, though no untrusted checkout or script-injection sink was found.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jms/serializer Version ^3.32.5 | — | — |
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.