No security policy or automated security scanning leaves limited protection around future changes. The release also has no license declaration or license file, complicating lawful reuse and redistribution.
39%
Total Score
0
38
50
The package has had no release in nearly seven years: its latest release was published in December 2019, and it has had zero releases in the last 12 months. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but that does not compensate for the prolonged lack of activity.
No declared license, detected license, or license file was found in the package or repository. That creates a genuine reuse and redistribution concern.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little external maintenance signal.
Composer is used for the build, which is appropriate for a Packagist package, but no security scanning tools are present. The missing scanning reduces assurance for future dependency or source changes.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.