The repository is not archived, and the artifact is easy to inspect. The single-user project has no security policy and does not mention the package in its README, limiting transparency.
52%
Total Score
50
75
75
The package has had only one release, published about 6 years and 9 months ago, with no releases in the last 12 months. This leaves little evidence of ongoing maintenance.
There were no commits or active maintainers in the last 3 months. Combined with the single-release history, this is evidence of a dormant project.
The repository name matches the package name, which supports the linkage, but its README does not mention the package. That makes the package's relationship to the repository less transparent.
The repository uses Composer for building, but no security-scanning tools were detected. For this small configuration package, that is a modest transparency gap rather than a severe risk.
No security policy was found in the repository. This weakens the project's documented process for reporting and handling issues.
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.