kpacha/suricate-config
The README, matching source repository, and MIT declaration make the package reasonably transparent. Its single-user ownership and lack of security tooling reduce confidence in ongoing support.
42%
Total Score
50
79
88
Health Score Breakdown
The last release was published over 11 years ago, with no releases in the past 12 months and only five releases overall. This is strong evidence of abandonment risk, despite the package not being deprecated.
The repository recorded zero commits and zero active maintainers in the past three months, consistent with the long release gap. No provided signal shows current maintenance capacity to offset this.
Only one registry publishing account is listed, and the project is owned by an individual rather than an organization. This leaves a thin apparent support base, although registry access alone does not prove who actively maintains the code.
Composer build tooling is present, but no security scanning tools were detected. The build setup supports basic reproducibility while offering limited evidence of ongoing security hygiene.
The linked repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though it is less severe than the inactivity evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Kpacha |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 kpacha/config Version ~0.1 | — | — |
kpacha/suricate-php-sdk Version ~1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 11 years ago
- Created
- 11 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.