The package is clearly licensed, has a usable README, and comes from an organization-owned project. Its absent tests and security policy, minimal adoption, and limited project activity reduce confidence for long-term use.
58%
Total Score
75
100
75
75
This is the package's only release, published about 16 months ago, with no releases in the last 12 months. That limited history and lack of ongoing releases weaken evidence of active maintenance.
There were no commits and no active maintainers in the last three months, consistent with the repository's last push being about 16 months ago. This is the strongest evidence of currently limited maintenance.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little independent evidence of adoption or review.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance concern, not a severe risk on its own.
The repository has no security policy. For a small package this is a limited governance gap, but it leaves vulnerability-reporting expectations undocumented.
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.