The Apache-2.0 license, stable versioning, and organization-owned repository provide useful transparency. The absent security policy and scanning reduce assurance about ongoing maintenance and response practices.
65%
Total Score
67
100
81
75
Only one registry account has publish access, which is a narrow publishing base. The organization-owned repository provides some backing, so this is not treated as a severe risk.
The package has 58 releases over roughly six years, but none in the last 12 months and the latest was in December 2024. This is a meaningful maintenance concern, partly offset by a repository push in December 2025.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the lack of recent registry releases, this indicates limited current development activity.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no external adoption signal to offset the maintenance concerns.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
intervention/image Version ^2.5 | — | — |
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.