It has a clear MIT license, repository tests, GitHub releases, and organization-backed ownership. The missing security policy and workflow weaknesses add operational uncertainty for a CLI distributed as a Phar.
58%
Total Score
75
94
75
The package has existed since August 2018 with 16 releases, but it made no releases in the last 12 months and its median release interval is about 127 days. This indicates materially reduced release activity.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, which is a strong recent-maintenance gap despite the repository not being archived.
The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
All 30 analyzed action references are unpinned, and a high-severity cache-poisoning finding has low confidence while a medium-severity archived-action finding has high confidence. The audit found no untrusted checkout or script-injection path, so this is workflow hygiene risk rather than a severe dependency verdict.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
fp-cli/fp-cli Version dev-main | — | — |
fp-cli/db-command Version ^2 | — | — |
fp-cli/core-command Version ^2.1 | — | — |
fp-cli/cron-command Version ^2 | — | — |
fp-cli/eval-command Version ^2 | — | — |
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.