griffbrad/composer-versioning-examples
The tiny artifact is easy to inspect, and its package and repository contents match. It has had no release or commit activity since May 2019, with no security scanning and no declared or detected license, making ongoing maintenance and reuse harder to trust.
45%
Total Score
0
75
75
Health Score Breakdown
The latest release was about 7 years ago, with no releases in the last 12 months; four releases were clustered on the first day. This is strong evidence of an abandoned or one-off package, although its example-package scope may reduce maintenance needs.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the release history and indicating no observed ongoing maintenance.
No license is declared, detected, or present in the package or repository. That creates a real legal-transparency gap for adoption.
Composer is used as a build tool, but no security scanning tool is present. This is a modest transparency and supply-chain hygiene gap, not evidence of malicious behavior.
The repository has no security policy. For a small example repository this is less serious than for a widely consumed library, but it still reduces transparency around vulnerability reporting.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 7 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.