ghostff/session
The license declaration conflicts with the BSD-4-Clause license file, and all two workflow actions are unpinned. A focused README, tests, release notes, stable version, and an active unarchived repository provide useful support despite no commits in the last three months.
62%
Total Score
50
100
86
100
Health Score Breakdown
The manifest declares 0BSD, but the artifact and repository license files identify BSD-4-Clause. The release is licensed, yet the mismatch creates real legal ambiguity.
The package has existed for over nine years with seven releases, but none were published in the last year and releases are widely spaced. This indicates a slow maintenance cadence, though the latest release is recent enough to show some continued stewardship.
The repository recorded no commits and no active maintainers during the last three months. That weakens evidence of ongoing maintenance, although the separate release and repository-push signals show the project is not clearly abandoned.
The single workflow was fully analyzed with no dangerous triggers, sinks, or audit findings, but both of its two action references are unpinned. This is a supply-chain hygiene gap rather than a severe risk on its own.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 ghostff |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 1 year 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.