Tests, a README, a matching repository, and an MIT license provide useful maintenance and usage context. The small maintainer base, absent security policy, and unpinned workflow actions add modest ongoing risk.
55%
Total Score
50
100
81
75
The package has had only 3 releases, all within about 5 days in September 2024, followed by no releases in the last 12 months. This is a substantial maintenance concern for a library dependency.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap. The repository is not archived, but current maintenance activity is absent.
Only one registry publishing account is listed, which is a modest resilience concern. The organization-owned repository makes a short registry maintainer list less significant than it would be for an individually owned project.
The project uses Make and Composer build tooling, but no security scanning tools were detected. The established build tooling is positive; absent scanning is a minor hygiene gap given the package's inactivity.
The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This is a transparency gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jtrw/dao Version * | — | — |
doctrine/dbal Version 4.* | — | — |
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.