CLI interface for the best htaccess tester in the world.
76%
Total Score
75
100
100
70
One workflow uses pull_request_target, which warrants care because that trigger can expose privileged workflow context, but no untrusted checkout or script-injection patterns were detected.
All recent commit activity comes from one contributor, creating a concentration risk; the organization-owned repository provides some capacity to hand maintenance off, but no second recent contributor is shown.
There was one commit by one active maintainer in the last three months, so maintenance is currently present but sparse.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented and reducing transparency for security issues.
None of the four analyzed workflows declares top-level token permissions. No workflow requests explicit top-level write access, but the lack of restrictive declarations leaves permissions less explicit than they should be.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ^7.0 || ^8.0 | — | — |
symfony/console Version ^7.0 || ^8.0 | — | — |
php-http/guzzle7-adapter Version ^1.0 | — | — |
http-interop/http-factory-guzzle Version ^1.0 | — | — |
madewithlove/htaccess-api-client Version ^3.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.