Tests, changelog, release notes, and MIT licensing make the project transparent and straightforward to inspect. Its last registry release was over nine years ago, and repository activity stopped over seven years ago, leaving maintenance and compatibility risk.
38%
Total Score
0
79
75
The package has had no releases in the last 12 months, and its latest release was in July 2017 despite a long publication history. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months; the last observed push was in April 2019, over seven years ago. The repository is not archived, but that does not compensate for the prolonged inactivity.
Composer is used for the build, but no security-scanning tooling is present. The missing scanning is a modest hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, though it is secondary to the prolonged inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jms/metadata Version ^1.5 | — | — |
nocarrier/hal Version ^0.9.11 | — | — |
jms/serializer Version ^1.0 | — | — |
guzzlehttp/guzzle Version ^6.1 | — | — |
doctrine/annotations Version ^1.2 | — | — |
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.