phrozenbyte/pico-theme
Clear licensing and packaging documentation reduce adoption friction. The small project footprint and absent security policy leave little room for confidence if maintenance needs arise.
45%
Total Score
0
100
75
75
Health Score Breakdown
The package includes a README and changelog, but the README explicitly identifies this as an unsupported fork and points users to Pico's end-of-life notice, materially increasing abandonment risk.
The repository recorded zero commits and zero active maintainers in the last 3 months, indicating no recent development capacity despite a recent registry release.
The package has 18 releases over roughly 9 years and one release in the last 12 months, showing a long history but a sparse current cadence.
No security policy was found in the repository, leaving vulnerability-reporting expectations unclear. This is a transparency gap, not evidence of malicious behavior.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Daniel Rudolf |
| The Pico Community |
| Contributors |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 phrozenbyte/pico Version self.version | — | — |
Weekly Downloads
Info
- Last Published
- 9 months 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.