kjdev/lz4
The package includes tests, a readable README, release notes, and only one runtime dependency. There is no security policy, but two maintainers remain active and the only workflow alert is a low-confidence cache concern.
82%
Total Score
100
100
94
67
Health Score Breakdown
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanner is a modest transparency gap, not evidence of unsafe code.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This lowers transparency but does not by itself indicate abandonment.
Both workflows were analyzed, use job-level permissions, and pin all eight action references. The auditor reported a high-severity cache-poisoning pattern with low confidence, so it is a hygiene caution rather than a severe standalone risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 1 year 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.