ibrcan/efatura
The package has a clear MIT license, README, tests, and a matching source repository. Its five runtime dependencies and unpinned workflow action are manageable, but the project shows no maintenance activity for nearly 4 years and 9 months.
38%
Total Score
25
100
80
83
Health Score Breakdown
The latest release was published nearly 4 years and 9 months ago, with no releases in the last 12 months. This is strong evidence of abandonment for a package handling invoicing integrations.
The repository recorded 0 commits and 0 active maintainers during the last 3 months, consistent with the long release gap and reinforcing the maintenance risk.
The package and repository are owned by the same individual account, so the source relationship is clear, but there is no organizational backing to compensate for the thin maintenance base.
The repository has no security policy or security scanning tools. This is a transparency and maintenance weakness, though it is secondary to the much longer inactivity period.
The single workflow was fully analyzed with no reported audit findings or dangerous triggers, but its one action use is unpinned. The missing top-level permissions block is acceptable on its own.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Furkan Kadıoğlu |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 mpdf/mpdf Version ^8.0 | — | — |
ramsey/uuid Version ^3.7|^4.0 | — | — |
guzzlehttp/guzzle Version ^7.4 | — | — |
kwn/number-to-words Version ^1.9 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 6 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.