jbzoo/composer-graph
Clear licensing, a substantial README, and release notes make the package easy to evaluate and adopt. The workflow has read-only permissions and no detected dangerous findings, though its action references are not pinned and no security policy is present.
84%
Total Score
100
94
67
Health Score Breakdown
The project uses Composer, Make, and Box build tooling, but no security scanning tools were detected; the missing scanning is a modest transparency gap rather than evidence of abandonment.
No repository security policy was found, leaving vulnerability-reporting expectations undocumented.
The single workflow was fully analyzed, uses read-only permissions, and has no dangerous or high-confidence audit findings. However, all 13 action references are unpinned, which weakens build reproducibility and supply-chain hygiene.
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 | — | — |
symfony/console Version >=7.3.4 | — | — |
jbzoo/mermaid-php Version ^8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 6 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.