takpesar/fruitcraft
The project has a clear README, MIT licensing, and a matching source repository. Its small release history and no recent commits leave maintenance uncertain, with no security policy or scanning.
57%
Total Score
50
100
79
75
Health Score Breakdown
The repository is owned by an individual user rather than an organization, so the project has limited visible institutional backing to compensate for a small maintainer base.
Only two releases exist over roughly 16 months, with no releases in the last 12 months; this provides limited evidence of sustained maintenance.
There were no commits and no active maintainers in the past three months, which is a concrete sign of inactive development and raises abandonment risk.
Composer is used for builds, but the repository has no security scanning tools. This is a hygiene gap that adds uncertainty without independently making the package unsafe to depend on.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Tak Pesar |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 1 year 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.