Protect symfony applications against CSRF attacks with the help of standard headers.
67%
Total Score
caution
Usable with caveats: long release gaps, single-maintainer activity, and workflow hygiene gaps temper otherwise solid packaging.
The repository is owned by an individual user rather than an organization, so the single-contributor maintenance concentration is not offset by visible organizational backing.
The package has only 5 releases over roughly 6 years, with a median interval of about 508 days. A release in the last 3 months is reassuring, but the overall cadence remains slow.
All 2 recent commits came from one contributor, giving the project a concentrated maintenance base without organizational backing shown by the provided ownership data.
There were 2 commits in the last 3 months, showing recent maintenance, but activity is still limited for a security-related bundle.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/config Version ^5.1 || ^6.0 || ^7.0 || ^8.0 | — | — |
symfony/http-kernel Version ^5.1 || ^6.0 || ^7.0 || ^8.0 | — | — |
symfony/http-foundation Version ^5.1 || ^6.0 || ^7.0 || ^8.0 | — | — |
symfony/dependency-injection Version ^5.1 || ^6.0 || ^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.