The package has a clear README, tests, a release note, and a small runtime dependency surface. Its same-day publication leaves no demonstrated maintenance record, while the repository has no security policy or scanning tools yet.
64%
Total Score
75
100
88
83
This is the package's first release and it was published today, so there is no track record for maintenance or issue response. The repository and release artifacts provide some initial transparency, but cannot establish long-term reliability.
There were no commits and no active maintainers during the last three months. Because the repository was created today, this is mainly missing evidence rather than proof of abandonment, but it still limits confidence in ongoing maintenance.
Composer build tooling is present, but no security scanning tools are configured. That is a meaningful transparency and maintenance gap for a newly published package, though it is not a standalone release blocker.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. The package's tests and documentation partially compensate for general project transparency, but not for security reporting.
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.