The repository has had no commits for more than eight years, with one registry maintainer and no security policy or scanning. A license, README, stable version, and no install scripts provide useful transparency but do not offset the abandonment risk.
35%
Total Score
25
100
78
75
The latest release was published more than eight years ago, and there were no releases in the last 12 months. This is strong evidence of abandonment for a package that may need compatibility updates.
The repository recorded zero commits and zero active maintainers in the last three months, with its last push also more than eight years ago. The lack of recent development materially increases maintenance risk.
Only one account has registry publishing access. With no organization backing shown and no recent activity, this indicates a thin maintenance base.
The repository has only 2 stars, 1 fork, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these low figures provide little evidence of a broad user or contributor community.
Composer is used for the build, but no security scanning tools are present. This is a modest supply-chain hygiene gap, though it is less significant than the stale maintenance signals.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
eveseat/web Version ^2.0 | — | — |
eveseat/eveapi Version ^2.0 | — | — |
eveseat/services Version ^2.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.