Clear documentation, MIT licensing, release notes, and no install scripts reduce adoption friction. The project is backed by an organization, but its operating history is still short.
68%
Total Score
67
100
93
75
One contributor made all 11 commits in the last three months. Organization backing provides some handoff capacity, but no second active contributor is evidenced.
Eleven commits in three months show recent work, though all activity came from one active maintainer, limiting evidence of distributed maintenance capacity.
Composer is used for builds, but no security scanning tool was detected. This is a modest transparency and maintenance gap rather than a release-blocking issue.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
All three workflows were analyzed cleanly with no untrusted checkouts, script injection, or high-severity findings. However, all three action references are unpinned, creating a workflow reproducibility and supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
liberusoftware/theme-base Version ^2.0 | — | — |
liberusoftware/theme-support Version ^1.0 | — | — |
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.