mariocoski/laravel-blogger
The README, tests, MIT license, and version notes make the package reasonably transparent. Its repository is not archived, but the long-running lack of releases and recent commits leaves adoption exposed to obsolete dependencies and missing fixes.
42%
Total Score
0
71
50
Health Score Breakdown
The latest registry release was in October 2017, with no releases in the last 12 months. This is strong evidence of abandonment for a package intended to be adopted as a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the release-history concern even though it was last pushed in March 2022.
Composer build tooling is present, but no security-scanning tools were detected. That limits evidence of ongoing dependency and vulnerability hygiene.
The repository has no security policy, leaving maintainers' vulnerability-reporting process unclear. This is a transparency gap, but it is secondary to the much older maintenance record.
Version v0.1.3 is not a stable major release, which adds maturity uncertainty, although it is not marked as a prerelease.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 laravel/scout Version ^1.0.0 | — | — |
laravel/tinker Version ^1.0 | — | — |
erusev/parsedown Version ^1.6 | — | — |
laravel/framework Version 5.4.* | — | — |
laravel/socialite Version ^3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 9 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.