The small repository is actively backed by an organization, with a matching README and a recent push. Workflow references are unpinned and the project has no security scanning, so maintenance and build hygiene deserve attention.
72%
Total Score
75
100
83
75
The package has existed for about 3 years and 5 months with 16 releases, but only one release in the last 12 months indicates a slow cadence. This is a modest maintenance concern rather than abandonment evidence because the repository was pushed recently.
The repository recorded zero commits and zero active maintainers in the last 3 months. For an automatically synchronized metapackage this may reflect its simple model, but it still limits evidence of ongoing maintenance.
The repository has 2 stars, 0 forks, and 1 watcher, showing very limited visible adoption. Popularity is only supporting evidence, so this is a minor concern rather than a health verdict.
Composer build tooling is present, but no security scanning tools were detected. For a tiny metadata-only repository this is a hygiene gap, not a severe supply-chain finding.
The repository has no security policy. This reduces disclosure transparency, although the package contains no runtime implementation and other signals show clear licensing and ownership.
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.