allowing/core
The repository has no security policy or security-scanning tooling, adding little oversight. Its minimal four-file layout also offers limited documentation and project evidence for a dependency.
30%
Total Score
100
61
67
Health Score Breakdown
This is the package's only release, published about 10 years ago, with no releases in the last 12 months. That strongly suggests abandonment risk, despite the package not being formally deprecated.
Neither the registry metadata nor the package or repository contains a recognized license. This creates a material legal and transparency problem for adoption.
The package and repository contain only four files: composer.json and two source files alongside .gitignore. That may be intentional for a tiny library, but it leaves little visible project structure to support long-term maintenance.
The artifact has no README, tests, or changelog, and the repository indicators also show no tests or changelog. While tests and changelogs need not ship in the artifact, the absent README and source-project documentation reduce consumer confidence.
The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these figures provide no supporting evidence of active community use.
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
- 10 years ago
- Created
- 10 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.