wislem/berrier
Documentation is incomplete, and security practices are thin. The MIT license, matching repository, and changelog improve transparency but do not offset the abandonment risk.
35%
Total Score
0
75
75
Health Score Breakdown
The latest registry release was in September 2016, with no releases in the last 12 months. This long release gap is strong evidence of abandonment risk.
The repository had zero commits and zero active maintainers in the last three months, consistent with its last push being in January 2017. That leaves current maintenance capacity unproven.
The artifact includes a README and changelog, but the README still contains template text such as “This is where your description should go.” The changelog partly compensates, but consumer documentation remains weak.
Composer is used as the build tool, but no security scanning tools are reported. For an old application package with many runtime dependencies, this is a maintenance and transparency gap.
The repository has no security policy. This makes vulnerability reporting and response expectations unclear, adding a modest maintenance concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Peter Lazaridis |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 bkwld/croppa Version ~4.0 | — | — |
kalnoy/nestedset Version ^4.0 | — | — |
caffeinated/menus Version ~2.0 | — | — |
devfactory/minify Version 1.0.* | — | — |
illuminate/console Version ^5.2 | — | — |
Weekly Downloads
Info
- Last Published
- 10 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.