h4zz4rddev/seat-buyback
Clear licensing, a readable README, and a matching organization-owned repository improve transparency. The project has no commits in three months and nine open issues, so future fixes may be slow.
65%
Total Score
63
100
94
83
Health Score Breakdown
Only one registry publishing maintainer is listed, which is a narrow release-control base, but the repository is organization-owned, making this less concerning than a similarly thin standalone project.
The repository recorded zero commits and zero active maintainers in the last three months, which is a meaningful maintenance concern despite the release published during the same period.
Nine issues remain open, with no issues or pull requests opened or closed in the last month; this suggests limited recent issue handling and weakens confidence in ongoing support.
Composer build tooling is present, but no security-scanning tools were detected, leaving a modest repository-hygiene gap.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 H4zz4rd |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 eveseat/api Version ^5.0 | — | — |
eveseat/web Version ^5.0 | — | — |
eveseat/eveapi Version ^5.0 | — | — |
eveseat/services Version ^5.0 | — | — |
Weekly Downloads
Info
- Last Published
- 11 months ago
- Created
- 4 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.