webmechanicx/streak
The single-maintainer project has no recent contributor activity and no security policy. A clear README, release notes, matching repository, and MIT license improve transparency, but the long release gap makes future fixes uncertain.
42%
Total Score
33
81
83
Health Score Breakdown
This package has had one release, with no releases in the last 12 months; the only release was nearly nine years ago. That long gap is strong evidence of abandonment risk for an API client.
There were no commits and no active maintainers in the last three months. Combined with the old last push shown by repository status, this indicates little current capacity for fixes.
Only one registry account has publish access, creating a thin publishing base. The matching repository and clear project ownership provide some continuity, so this is a caution rather than a severe risk.
The package and repository are owned by the same individual account rather than an organization. That makes the single-maintainer concern more significant because no organizational backing is shown.
The repository uses Composer build tooling, which fits the package ecosystem, but it has no reported security scanning. This is a modest transparency and maintenance gap rather than a severe risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Farhadur Rahim |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 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.