deboorn/escrow-api
The package is clearly identified and includes a README, MIT license, and release notes. Support depends on one maintainer, with no security policy or scanning and no recent development. Expect compatibility work to be yours.
42%
Total Score
25
79
50
Health Score Breakdown
This is the package's only release, published about nine years ago, with no releases in the last 12 months. That strongly indicates abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and leaving current compatibility issues unaddressed.
One registry maintainer creates a thin support base. The user-owned repository provides no organizational backing to compensate for that concentration.
Composer build tooling is present, but no security scanning tools are configured. For a package handling escrow API credentials, this is a modest maintenance and transparency gap.
The repository has no security policy, leaving no documented process for reporting or handling security issues. This is a transparency gap, though not evidence of malicious behavior.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Daniel Boorn |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 9 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.