i4n/phpjasper
The MIT license, detailed README, and matching source repository improve transparency. No security policy and no recent development activity leave maintenance and future fixes uncertain.
35%
Total Score
25
75
75
Health Score Breakdown
The package has made only two releases, both in January 2018, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the stable 2.20 version.
There were zero commits and zero active maintainers in the last three months, consistent with the repository having been inactive since January 2018. This substantially raises abandonment and future-fix risk.
The repository is owned by an individual rather than an organization, so there is no observed organizational backing to compensate for the inactive maintenance record.
Composer build tooling is present, but no security scanning tooling was detected. The missing security checks are a transparency and maintenance weakness, though not as significant as the inactivity.
The repository is not marked archived, but its last push was in January 2018; the unarchived status does not compensate for the prolonged inactivity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Vinicius Azevedo |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 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.