abuseio/parser-iecccom
The small, focused artifact has a clear GPL-2.0 license, matching source repository, and only two runtime dependencies. Organization backing helps, but the package remains untested and lacks a security policy.
46%
Total Score
50
72
50
Health Score Breakdown
The latest release was published in August 2018, with no releases in the last 12 months. That long gap materially raises abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and limited maintenance visibility.
The package includes a README, but it explicitly says the parser is untested; no tests or changelog are present. Missing tests are not inherently a packaging gap, but the stated lack of coverage weakens confidence in changes.
The repository has one star and one fork, indicating a very small user and contributor footprint. Popularity is only supporting evidence, but it offers little compensating evidence for the maintenance gap.
Composer build tooling is present, but no security scanning tools are configured. That provides basic build structure without evidence of automated security oversight.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 AbuseIO Foundation |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 abuseio/parser-common Version 1.2.* | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 10 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.