The repository is maintained by an organization, matches the package, and documents this release with notes. Recent commit activity is currently quiet, and the single workflow uses an unpinned action; there is also no security policy or scanning tool.
68%
Total Score
75
100
88
75
The package is about 2 years and 11 months old with 10 releases and one release in the last 12 months. This shows ongoing publication but a currently modest cadence.
There were no commits and no active maintainers in the last 3 months. The recent release and February push partly offset this, but the present maintenance signal is quiet.
Composer build tooling is present, but no security scanning tools were detected. That is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. For a small integration this is a transparency gap, but it is not by itself evidence of abandonment.
The only workflow was fully analyzed, scopes permissions at job level, and has no dangerous triggers or audit findings. Its one action use is unpinned, leaving a modest reproducibility and supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^5.0.0-beta.5 | — | — |
verbb/formie Version ^3.0.0-beta.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.