capell-app/blog
The repository is actively changed and releases are frequent, with clear documentation and source alignment. Maintenance is concentrated in one contributor, and its workflow combines untrusted checkout with broad write access and unpinned actions.
64%
Total Score
83
100
75
Health Score Breakdown
One contributor made all 19 recent commits, creating a real continuity risk. Organization ownership provides some ability to hand maintenance off, so this is a caution rather than a severe abandonment signal.
The repository has no security policy, leaving no visible process for reporting or coordinating security issues. This is a transparency and maintenance gap.
The only workflow uses pull_request_target with an untrusted checkout and top-level write permissions, so repository-controlled changes may reach a broadly scoped token. Both analyzed actions are also unpinned, weakening build reproducibility.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Howdu |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 capell-app/core Version ^1.0.21 | — | — |
capell-app/tags Version ^1.0 | — | — |
capell-app/admin Version ^1.0 | — | — |
capell-app/frontend Version ^1.0.25 | — | — |
capell-app/html-cache Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 14 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.