bookfrank/stylite-blog
The MIT license, readable documentation, and release notes improve transparency. No security policy or security scanning leaves maintenance practices less visible.
42%
Total Score
0
79
50
Health Score Breakdown
The package has had only one release, published nearly nine years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the stable version label.
The repository recorded no commits and no active maintainers in the last three months, reinforcing the long release gap and indicating no recent maintenance.
Composer is used for the build, which is a positive reproducibility signal, but no security scanning tools are configured. The missing scanning is a modest hygiene concern rather than proof of unsafe code.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap for a web application.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Frank |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 twig/twig Version 1.24.0 | — | — |
erusev/parsedown Version 1.6.0 | — | — |
bookfrank/viaduct Version 1.1.0 | — | — |
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.