szeidler/composer-patches-cli
It has clear licensing, tests, release notes, and a repository that matches the package. The workflow uses two unpinned actions, while no security scanning or security policy is reported.
72%
Total Score
50
100
93
75
Health Score Breakdown
No commits or active maintainers were recorded in the last three months. That is a maintenance concern, though it is partly offset by the release made within the observed period.
Composer build tooling is present, but no security scanning tools are reported. The missing scanning is a hygiene gap rather than evidence of abandonment.
The repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, with no provided signal compensating for that gap.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings, but both referenced actions are unpinned. Missing top-level permissions is acceptable here because the workflow does not request broad write access.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 cweagans/composer-patches Version ^1.7 || ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 months ago
- Created
- 6 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.