jbzoo/ci-report-converter
Clear documentation, repository tests, and a recent major release make the project straightforward to evaluate. Workflow dependencies are not pinned, and recent maintenance is concentrated in one contributor despite organization backing.
72%
Total Score
83
100
50
Health Score Breakdown
All four recent commits came from one contributor, concentrating current maintenance responsibility. Organization ownership provides some capacity for handoff, but no second recent contributor is shown.
No repository security policy was found, leaving vulnerability-reporting guidance unclear. This is a transparency gap, not evidence that the package is unsafe.
All 24 analyzed action references are unpinned, and the audit found a high-confidence unpinned container image in action.yml. No untrusted checkout or script-injection path was reported, limiting this to a workflow hygiene and reproducibility concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Denis Smetannikov |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 jbzoo/cli Version ^8.0 | — | — |
jbzoo/data Version ^8.0 | — | — |
jbzoo/utils Version ^8.0 | — | — |
jbzoo/markdown Version ^8.0 | — | — |
symfony/console Version >=7.3.4 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 5 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.