markmercedes/trest
Tests, a README, and an MIT declaration provide useful adoption context. The project has no security scanning or policy, and its single-maintainer history has been inactive since April 2016.
35%
Total Score
25
71
75
Health Score Breakdown
The latest release was in April 2016, with no releases in the last 12 months; this long publishing gap is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating no current maintenance.
One registry maintainer is a small ownership base for a library, increasing continuity risk; the linked repository is also owned by an individual rather than an organization.
Composer build tooling is present, but no security scanning tools were detected, leaving a transparency and maintenance-hygiene gap.
The linked repository is not archived, although its last push was in April 2016; the inactive history remains the stronger concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 markmercedes |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 12 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.