A clear MIT license, focused README, and organization-owned repository improve transparency. The workflow uses read-only job permissions, but its two actions are unpinned and no security policy or scanner is present.
60%
Total Score
75
100
88
50
The package has only 2 releases, with none in the last 12 months; the latest release was 19 months ago. This weakens confidence in ongoing maintenance, although the repository remains active enough to avoid treating the package as abandoned outright.
There were 0 commits and 0 active maintainers in the last 3 months. Combined with no releases in the last year, this is a meaningful maintenance concern.
Composer is used for the build, but no security scanning tool is configured. That is a transparency and hygiene gap, though it is not evidence that the release is unsafe by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a modest transparency gap for a dependency.
The only workflow was fully analyzed, uses read-only job permissions, and has no reported audit findings. However, both of its 2 action references are unpinned, creating a supply-chain hygiene weakness.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/finder Version ^4 || ^5 || ^6 | — | — |
contao/core-bundle Version ^4.9 || ^5 | — | — |
symfony/filesystem Version ^4 || ^5 || ^6 | — | — |
symfony/webpack-encore-bundle Version ^1.12 || ^2.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.