The tiny artifact has no README, tests, or changelog, limiting transparency and consumer confidence. Composer is used for builds and the repository is not archived, but the project has had no releases or commits for about nine years.
38%
Total Score
50
100
69
75
The package has had only two releases, both on March 1, 2017, with no release in about nine years. This is strong evidence of abandonment for a dependency, despite the package not being deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with no activity since March 2017. This materially increases abandonment risk.
The package and repository each contain only three files, including one PHP source file and composer.json. Such a small implementation can be reasonable for a narrowly scoped WordPress filter, but it provides little supporting documentation or project context.
The published artifact has no README, tests, or changelog. Although tests and changelogs normally belong in the repository, the missing README reduces consumer transparency for this PHP package.
Composer is used as a build tool, which supports reproducible package handling, but no security scanning tools are present. The missing scanning is a hygiene gap, not evidence that the release is unsafe by itself.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.