The package is clearly licensed, has one runtime dependency, and is backed by an organization-owned repository. Its very small footprint and lack of security scanning or a security policy leave less evidence for long-term maintenance.
48%
Total Score
75
100
81
75
This is the package's only release, published about 16 months ago, with no releases in the last 12 months. That provides limited evidence of ongoing maintenance and lowers adoption confidence.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the single-release history, this is a meaningful abandonment concern.
The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these counters provide no supporting evidence of an active user or contributor community.
The repository uses Composer, but no security scanning tools were detected. For a small package this is a hygiene gap rather than a severe risk, though it reduces transparency around maintenance practices.
No repository security policy was found. This does not prove unsafe maintenance, but it removes a useful channel for reporting and documenting security issues.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
litefyr/integration Version self.version | — | — |
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.