happy-types/enumerable-type
Its documentation, tests, licensing, and dependency footprint are solid. There is no security scanning or policy, and the project has only one registry maintainer.
55%
Total Score
50
100
88
83
Health Score Breakdown
The repository is owned by an individual rather than an organization, so continued maintenance depends on a single project owner. This adds some continuity risk alongside the observed inactivity.
The package has only three releases since March 2017, with no releases in the last 12 months and the latest release in February 2019. That is a substantial maintenance concern for a dependency.
There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive for years. This raises abandonment and compatibility risk.
Composer is used for the build, but no security scanning tool is configured. The missing scanning is a hygiene gap for a package intended to be consumed as a dependency.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, though it is not evidence of a vulnerability.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Antanas Arvasevicius |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 9 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.