The package is small and documented with tests, and its repository matches the package. No security policy, one registry maintainer, and minimal repository adoption leave little visible support.
43%
Total Score
25
72
50
Only two releases were published, both about 11 years ago, with none in the last 12 months. This is strong evidence of abandonment despite the package not being deprecated.
There were 0 commits and 0 active maintainers in the last 3 months, consistent with the repository's long inactivity and increasing abandonment risk.
The repository is owned by an individual account rather than an organization, so there is no shown organizational backing to offset the thin maintenance evidence.
The repository has 0 stars, 1 fork, and 1 watcher, indicating very limited visible adoption. Popularity is supporting evidence, but it reinforces the maintenance concern here.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a minor transparency gap rather than proof of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
itlife/session Version ~1 | — | — |
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.