The package has a clear README, MIT licensing, repository tests, and a recent release with notes. One maintainer, no security policy or scanning, and limited recent repository activity reduce confidence in long-term resilience.
68%
Total Score
50
93
50
The registry lists one maintainer, and the project is backed by a user-owned repository rather than an organization. This creates a thinner continuity path if that maintainer becomes unavailable.
The repository had zero commits and zero active maintainers in the three months before collection. The recent release partly offsets this, but the lack of ongoing activity is a maintenance concern.
There were no new or closed issues or pull requests in the last month, with four issues open. This is limited evidence of current project engagement, though it does not establish abandonment by itself.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy. That reduces transparency about vulnerability reporting and response expectations, although it does not by itself indicate poor code quality.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/framework-bundle Version ^6.4|^7.4|^8.0 | — | — |
mark-gerarts/auto-mapper-plus Version ^1.3 | — | — |
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.