Tests, release notes, and clear licensing improve day-to-day confidence. The organization-backed repository is not archived, but its lack of security scanning leaves a smaller transparency gap.
64%
Total Score
75
100
88
75
The package has only two releases, both within about two days, and no releases in roughly five months. That short history and subsequent pause make long-term maintenance uncertain.
There were zero commits and zero active maintainers in the last three months. For a package only about five months old, that is a meaningful maintenance concern.
Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence that the release is unsafe.
The repository has no security policy. That weakens the project's documented vulnerability-reporting process, though it is not by itself evidence of abandonment.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
symfony/form Version ^8.0 | — | — |
scafera/kernel Version ^1.0 | — | — |
symfony/validator Version ^8.0 | — | — |
symfony/security-csrf Version ^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.