crowdsec/capi-client
The release includes tests, release notes, a clear MIT license, and security tooling. The repository’s package naming mismatch and absent security policy add transparency concerns.
61%
Total Score
75
100
94
75
Health Score Breakdown
The repository recorded zero commits and zero active maintainers in the last 3 months, which is a meaningful maintenance concern despite the recent release.
The repository name does not match the package name and its README does not mention the package, making the source relationship less transparent even though the repository appears related to the client project.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
All 15 analyzed action references are unpinned, and the audit found four high-confidence template-injection findings plus an ad hoc package install. Read-only permissions and no untrusted checkout or dangerous trigger reduce the impact, but the workflow hygiene remains a concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 CrowdSec |
| Julien Loizelet |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 symfony/uid Version ^5.4.19 || ^6.2.5 || ^7.2.0 | — | — |
symfony/config Version ^4.4.44 || ^5.4.11 || ^6.0.11 || ^7.2.0 | — | — |
crowdsec/common Version ^3.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 3 months ago
- Created
- 4 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.