Question 1

Does ShieldCI read my Enlightn config?

Accepted Answer

No. Enlightn names checks by PHP class and ShieldCI uses short analyzer IDs, so the settings do not map one to one. Publish config/shieldci.php and list the checks you want off under disabled_analyzers, then run php artisan shield:baseline to snapshot the findings you already know about. Commit the .shieldci-baseline.json it writes and add --baseline to shield:analyze in CI, so only new findings fail the build.

Question 2

What about the Enlightn forks?

Accepted Answer

exin/enlightn adds Laravel 12 support to the original code, and LaraBeacon is a fork for Laravel 12 and 13. Both are reasonable if you want to stay on Enlightn's code. See ShieldCI vs LaraBeacon.

Question 3

What about enlightn/security-checker?

Accepted Answer

It checks Composer packages for known vulnerabilities and has not changed since December 2023. Composer's built-in composer audit does the same job, and ShieldCI checks Composer dependencies against the OSV database and npm dependencies with npm audit, as part of every run.

Question 4

Is ShieldCI free?

Accepted Answer

The open-source package, with 73 analyzers, is free under the MIT license. Paid plans add 82 Pro analyzers and the hosted dashboard, from $9 a month.

Question 5

Is ShieldCI affiliated with Enlightn?

Accepted Answer

No. ShieldCI is an independent project with its own codebase.

Feature	ShieldCI	Enlightn
Actively maintained		Archived Jan 2026
Laravel versions	9+	9 to 11
Free checks	73	66
Paid checks	82 more (Pro)	64 more (Pro)
Code quality and best-practice checks		—
Runs locally from Artisan
Baseline for existing issues
CI mode
Open-source license	MIT	LGPL-3.0

Enlightn was archived. Here is how ShieldCI compares.

ShieldCI and Enlightn compared

Switch from Enlightn in five minutes

Frequently asked questions

Close the loop on every finding.