Documentation, tests, licensing, and organization backing are present. The project has no security policy or security scanning, so maintenance coverage is thin.
42%
Total Score
67
75
50
The package has only two releases, with none in the last 12 months; its latest release was about 10 years ago. This is strong evidence of abandonment risk, although the repository is not archived.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The non-archived status and organization ownership provide limited compensation but do not show active maintenance.
There were no new or closed issues or pull requests in the last month. With no recent commits, this reinforces the lack of current project activity rather than demonstrating efficient issue handling.
Composer build tooling is present, but no security scanning tools were detected. This is a maintenance and transparency gap for a dependency project.
The repository has no security policy. The README provides a security contact, but no formal policy or process is present.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jms/serializer Version >=0.14 | — | — |
symfony/symfony Version ^2.6 | — | — |
jms/serializer-bundle Version ^0.13|^1.0 | — | — |
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.