The README, tests, MIT license, and release notes make integration and ownership clear. A single maintainer and unpinned CI actions leave less depth for future fixes.
58%
Total Score
50
92
50
The registry lists one maintainer, which limits publishing redundancy for a small package. The linked repository belongs to the same individual, so there is no separate organizational backing to compensate for that narrow base.
The package has had no release in over three years despite 12 releases overall, which is a meaningful maintenance concern. Its earlier release cadence shows the project was previously active, but does not offset the current gap.
The repository recorded 0 commits and 0 active maintainers in the last three months, indicating little recent development activity. This is consistent with the long release gap and raises abandonment risk.
No repository security policy was found, leaving vulnerability-reporting expectations undocumented. This is a transparency gap, though it is less serious than evidence of unsafe workflow behavior.
The single workflow was fully analyzed with no dangerous triggers, injection findings, or high-severity issues. However, both action references are unpinned, leaving the CI supply chain less reproducible.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
elegant-bro/arrayee Version ^0.1.0 | — | — |
elegant-bro/stringify Version >=0.3.1 | — | — |
otis22/php-interfaces Version ^1.1 | — | — |
elegant-bro/interfaces Version ^1.1 | — | — |
otis22/vetmanager-token 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.