The package includes a README, extensive tests, and a stable version, while its organization-owned repository matches the package. It has no license evidence and no security scanning, increasing adoption and maintenance risk.
44%
Total Score
50
100
67
83
The latest release was published about 7 years ago, with no releases in the last 12 months. This is strong evidence of abandonment despite the package having nine historical releases.
The repository recorded zero commits and zero active maintainers over the last 3 months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
Neither the package nor the linked repository declares or contains a recognized license. That creates a material legal and transparency concern for dependency adoption.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence of abandonment on its own.
The repository has no security policy. This weakens vulnerability-reporting transparency, although it is less significant than the lack of recent development activity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
anomaly/blocks-module Version ^1.2.0 | — | — |
anomaly/image-field_type Version ~1.3.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.