A single publisher and no security policy reduce resilience if maintenance is needed. MIT licensing, a documented README, repository tests, and a modest dependency set make the package transparent to adopt, but do not offset the age concerns.
48%
Total Score
25
100
81
50
The latest release was about 6 years ago, with no releases in the last 12 months. This is a substantial maintenance concern for a library dependency.
The repository recorded zero commits and zero active maintainers over the last 3 months, reinforcing the abandonment concern indicated by the old release.
There were no new or closed issues or pull requests in the measured month, while several issues and pull requests remain open. This supports a caution about inactive project management.
The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning is a minor transparency and maintenance gap.
No security policy was found in the repository. This weakens the project's process transparency, though it is not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flow/jsonpath Version ^0.3.1 | — | — |
illuminate/container Version ^5.0|^6.0|^7.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.