The recent pause in commits and single registry maintainer reduce confidence in ongoing support. Strong release cadence, tests, release notes, licensing, and Dependabot provide meaningful reassurance, but workflow checks still need attention.
68%
Total Score
50
100
94
67
The repository is owned by a personal user account rather than an organization. Combined with one registry maintainer and no recent active maintainers, this indicates a thin support base.
The repository recorded zero commits and zero active maintainers in the last 3 months. This is a meaningful maintenance concern, although the recent release history shows the project was active over the preceding year.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these numbers provide little external evidence of maturity or community support.
The repository has no security policy. This is a transparency gap for reporting vulnerabilities, though it is not by itself evidence of unsafe code.
All four workflows were analyzed, but all 9 action references are unpinned, three workflows grant top-level write permissions, and a high-confidence bot-conditions finding reports spoofable actor context in the auto-merge workflow. No untrusted checkout or script-injection paths were found, which limits the severity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
rodneyrehm/plist Version ^2.0 | — | — |
illuminate/collections Version ^11.0|^12.0|^13.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.