orkan/winamp
Clear usage instructions, a changelog, and matching source files make the package understandable to adopt. Its single maintainer and absent recent activity make long-term support uncertain, while no security policy adds a smaller transparency gap.
58%
Total Score
63
78
75
Health Score Breakdown
Only one registry account has publishing access. The linked repository is user-owned rather than organization-backed, so there is little observed publishing redundancy.
Although the package has 30 releases over nearly five years, it has had no release in the last 12 months; this indicates a meaningful maintenance slowdown.
There were zero commits and zero active maintainers in the last three months, showing no current development activity and increasing abandonment risk.
There are no open issues or pull requests and no recent issue or pull-request activity. This is compatible with a small stable tool, but provides no evidence of active support.
The repository has only 2 stars, 0 forks, and 1 watcher. Popularity is not decisive, but this leaves little community evidence to compensate for the single-maintainer, inactive project.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Orkan |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 orkan/utils Version ^8.0 | — | — |
symfony/finder Version ^5.2 | — | — |
symfony/console Version ^5.2 | — | — |
james-heinrich/getid3 Version ^1.9 | — | — |
symfony/monolog-bridge Version ^5.2 | — | — |
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 5 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.