The package has a clear README, tests, a license, and an organization-owned repository. Its tiny dependency surface and matching repository support adoption, but there is little evidence yet of sustained maintenance or security process.
62%
Total Score
75
100
81
50
This is the package's only release, published 134 days ago, so there is limited evidence of an established release cadence. The repository and package documentation provide some transparency, but do not demonstrate ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. That is a meaningful maintenance concern for a package whose only release is already 134 days old.
Composer build tooling is present, but no security-scanning tools were detected. This is a process gap rather than evidence of unsafe code, and the package's tests and minimal dependency surface provide some compensation.
The repository has no security policy, leaving disclosure and response expectations undocumented. This lowers transparency, though the package is a small contract library with no lifecycle scripts.
Version v0.1.0 indicates an early API and limited maturity, although it is not marked as a prerelease. The package's focused contracts and tests partly reduce adoption risk.
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.