The project has a clear README, an MIT declaration, and recent registry and repository activity. Organization backing offsets the single active contributor, but workflow pinning and the lack of a security policy reduce transparency.
76%
Total Score
100
93
50
Composer install and update lifecycle scripts are present, so installation performs package-defined actions beyond ordinary file extraction. The signal gives no evidence that those scripts are unsafe, making this a limited supply-chain caution rather than a severe risk.
Composer build tooling is present, but no security-scanning tool was detected. This is a transparency and maintenance gap, though it is not evidence of a defect in the release.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This lowers transparency but does not by itself indicate abandonment.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, both action references are unpinned, so their contents can change without a repository commit.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^13.0 || ^14.0 | — | — |
knplabs/github-api Version ^3.16 | — | — |
php-http/guzzle7-adapter Version ^1.1 | — | — |
m4tthumphrey/php-gitlab-api Version ^11.13 || ^12.0 | — | — |
code711/siteconfigurationevents Version ^2.0 || ^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.