Clear licensing, repository tests, and release notes provide useful transparency for consumers. The project has one registry maintainer and no security policy, so continuity and response practices are less clear.
58%
Total Score
50
88
75
Only one account has registry publishing access. Because the project is user-owned rather than organization-backed, this leaves a thin publishing and continuity base.
The registry namespace and repository owner are the same user account, showing ownership alignment but no organizational backing. This provides attribution without adding maintainer depth.
The package has 32 releases but none in the last 12 months, and its latest registry release was on April 23, 2019. This is a substantial freshness concern, though the linked repository was pushed more recently.
There were zero commits and zero active maintainers in the last three months. Combined with the lack of recent registry releases, this raises abandonment risk, although the repository is not archived.
The repository has 9 open issues and 6 open pull requests, but recorded new or closed issues and pull requests were all zero in the last month. This supports the broader concern that active maintenance is limited.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ~1.0 | — | — |
clue/graph Version ~0.8 | — | — |
symfony/yaml Version ~4.2 | — | — |
symfony/finder Version ~4.2 | — | — |
graphp/graphviz Version ~0.2.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.