fralik/package
The package is small and tested, with a clear README and minimal runtime dependencies. Its absent security policy leaves little visible guidance for reporting or handling future issues.
49%
Total Score
0
100
57
75
Health Score Breakdown
No declared license, license file, or repository license file was detected. The README mentions MIT, but that publisher text is not a license indicator and cannot compensate for the missing license evidence.
Only two releases exist, both published on January 11, 2023, with no releases in the last 12 months. This indicates a largely inactive release history.
There were no commits and no active maintainers in the three months measured; the repository was last pushed about three years and eight months ago. This is strong evidence of abandonment risk.
Composer is used for the build, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than a severe risk for this small package.
The repository has no security policy. This reduces transparency about vulnerability reporting, though it does not by itself show that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Timur Fralik |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 3 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.