The package has clear ownership, a license, and practical documentation, but no security policy or scanning leaves little evidence of protective maintenance. Its small project footprint also limits confidence in long-term support.
45%
Total Score
50
86
75
Only one registry maintainer is listed, which increases continuity risk for a small, independently owned project. The repository is correctly linked to the same owner, but no broader backing is shown.
The last release was in September 2016, with no releases in the past 12 months. This long release gap is strong evidence that maintenance has stopped, despite seven historical releases.
The repository recorded zero commits and zero active maintainers in the past 3 months, and its last push was in September 2017. That leaves little evidence of current maintenance capacity.
Composer build tooling is present, but no security-scanning tools are configured. That is a modest maintenance and transparency gap rather than evidence of unsafe code.
No security policy was found in the repository. This does not prove a security problem, but it reduces transparency for reporting and handling issues in an already inactive project.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phile-cms/phile Version >=1 | — | — |
infostreams/snippets Version >=1.1 | — | — |
phile-cms/plugin-installer-plugin Version >=1 | — | — |
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.