Filament settings page for laravel-security-headers: edit the Content Security Policy, response headers and HSTS from the panel, with a report-only mode to try a policy before enforcing it.
68%
Total Score
caution
A same-day release with no observed commit activity leaves maintenance maturity unproven, despite solid repository hygiene.
The package runs a post-autoload-dump install-time script. This is a supply-chain surface worth noting, but the signal provides no evidence that the script is unsafe.
One registry maintainer is responsible for publishing the package, which limits the visible publishing base; the linked repository confirms matching individual ownership but does not provide broader maintainer capacity.
The registry namespace and repository are owned by the same individual account, which is consistent ownership but does not provide organization-level backing or redundancy.
The package is 0 days old, with all 3 releases published on the same day and no established release interval, so maintenance maturity is not yet demonstrated.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, but the package is only 0 days old, making this primarily an absence of demonstrated history rather than evidence of collapse.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filament/filament Version ^5.3 | — | — |
spatie/laravel-settings Version ^3.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
filament/spatie-laravel-settings-plugin Version ^5.3 | — | — |
jeffersongoncalves/laravel-security-headers Version ^2.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.