static blog generator
61%
Total Score
caution
Usable with caveats: maintenance has gone quiet for three months despite a recent release.
Only one registry account has publish access, which is a narrow publishing base. The organization-owned repository provides some backing, so this is not treated as a severe concern.
The repository recorded zero commits and zero active maintainers in the last three months. A release during that period provides some counterevidence, but the lack of observed development activity still raises maintenance risk.
The project uses Make, Composer, and Box for builds, but no security-scanning tool was detected. That leaves a meaningful transparency and maintenance gap.
The repository has no security policy, so vulnerability reporting and response expectations are not documented.
v0.6.7 is not a stable-major release, so the API may still change before 1.0. It is not marked as a prerelease, which limits the concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ^6.0 | — | — |
cboden/ratchet Version ^0.4.4 | — | — |
illuminate/view Version ^v10.0 | — | — |
erusev/parsedown Version ^1.7 | — | — |
tempest/highlight Version ^2.11.2 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.