Releases are regular, and the package includes tests, release notes, clear licensing, and a focused dependency set. The organization-backed repository is active, but security policy and automated security scanning are absent.
68%
Total Score
67
100
81
83
One contributor made all commits in the last three months, creating a concentrated maintenance dependency. Organization ownership provides some handoff capacity, but no second active contributor is shown.
Only three commits were recorded in the last three months, indicating modest recent activity. The recent release and current repository state provide some compensation, but not evidence of a broad maintenance effort.
The repository has zero stars, forks, and watchers. For a package only about five months old this is limited supporting evidence, but popularity is not decisive by itself.
Composer build tooling is present, but no repository security-scanning tool was detected. The missing scanner is a modest process gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This lowers transparency for a runtime package.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
symfony/runtime Version ^6.4 || ^7.0 || ^8.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.