jrdev/drange
Usable with caveats: the release is licensed, tested, documented, recently updated, and has no deprecation or workflow red flags. Maintenance is concentrated in one contributor, and the package has released only three times over roughly nine years, so long-term continuity is less certain.
74%
Total Score
75
100
88
67
Health Score Breakdown
The package is mature but has only three releases since 2017, with a typical interval of roughly four years, indicating a sparse release cadence despite the latest release being recent.
All 11 recent commits came from one contributor, leaving maintenance dependent on a single person and creating a genuine continuity risk.
Composer build tooling is present, but no security scanning tools were detected; this is a modest transparency gap rather than a direct adoption blocker.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
The workflow does not declare top-level token permissions, so its intended permission scope is less explicit than best practice.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jose Robinson |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 4 months 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.