Its MIT license, small dependency surface, and matching repository make adoption straightforward. The lack of security scanning and very small public footprint leave little evidence of ongoing support.
44%
Total Score
0
100
79
67
The package is about four years old, has only three releases, and has had no release in the last 12 months. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in September 2022. No provided maintenance signal compensates for this inactivity.
The repository has zero stars, forks, and watchers, providing little evidence of community use or outside review. Popularity is supporting evidence rather than decisive on its own, but it reinforces the maintenance concern.
The repository has no security policy, leaving no documented reporting path. This is a transparency and maintenance gap, though it is less serious than the long-term inactivity.
The single workflow uses a pull_request_target trigger, but the audit found no untrusted checkout or script-injection sink. Its one action reference is unpinned, which is a modest supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
php-flasher/flasher Version ^1.7 | — | — |
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.