The MIT license, tests, release notes, and organization-backed repository provide useful support. The missing security policy and package-name mismatch make the project less transparent, while workflow references are not pinned.
68%
Total Score
83
100
94
50
The package defines a post-install command. Install-time code increases dependency-installation exposure, although this signal alone does not show that the script is unsafe.
The repository recorded zero commits and zero active maintainers in the last three months. That is a meaningful maintenance warning, even though the release history shows the package has been updated over time.
The repository name does not exactly match the package name and its README does not mention the package. That may reflect a naming or monorepo relationship, but it still reduces confidence that the linked repository is specifically documented for this package.
No repository security policy was found. This reduces transparency for reporting and handling vulnerabilities, though it is not by itself evidence that the package is unsafe.
All five workflows were analyzed with no reported audit findings or untrusted checkout and script-injection sinks. However, all four action references are unpinned, weakening build reproducibility and exposing workflow execution to upstream action changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ^6.3 || ^7.4.7 | — | — |
symfony/config Version ^6.3 || ^7.4.7 | — | — |
symfony/dotenv Version ^6.3 || ^7.4.7 | — | — |
symfony/http-kernel Version ^6.3 || ^7.4.7 | — | — |
atoolo/search-bundle Version ^1 | — | — |
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.