AGPL-3.0 §13 network-use disclosure
You declared modified: true and network_exposed: true. AGPL-3.0 §13 attaches an obligation the moment both are true — and it attaches to the users of your service, not to the people you distribute to.
The clause
Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) the opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. AGPL-3.0-only §13 · gnu.org/licenses/agpl-3.0.txt · retrieved 2026-09-20
Evidence
The finding resolves to a file and a line range. Nothing in this verdict is asserted without one — a test fails the build on any rendered finding that lacks a citation.
1 GNU AFFERO GENERAL PUBLIC LICENSE 2 Version 3, 19 November 2007 3 4 Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/> 5 Everyone is permitted to copy and distribute verbatim copies 6 of this license document, but changing it is not allowed. 7 8 Preamble 9 … 508 13. Remote Network Interaction; Use with the GNU General Public License.
Why it fired — the predicate trace
Every finding carries the predicate that produced it, evaluated against your declared intent. This is the whole reason the decision layer is pure: the same trace reproduces the same finding, forever.
Suggested fix
Swap firecrawl for crawl4ai — Apache-2.0, same capability, no §13 obligation under your intent.
A fix is a suggestion, never an instruction. Its confidence is stated separately from the finding's — a HIGH finding can carry a MEDIUM fix, and the interface says so.
What would change this verdict
If you consume firecrawl unmodified, §13 does not attach. Note that patching a single vendored file counts as modification — the common misconception runs the other way.
A local CLI that never offers the software over a network is outside §13 — but the GPL distribution duties in §4–6 still apply if you ship the binary.
How a MEDIUM finding reads differently
Ambiguity is not hidden in a tooltip. When confidence is below HIGH, the interface shows the exact text that is ambiguous, and the reading that was rejected.
A commercial gate applies above 1,000 monthly active users.
The gate applies at 1,000 MAU, and you declared 5,000.
"whichever is later" could extend the window to 12 months regardless of MAU.
Both readings are shown because the clause genuinely supports both. Clearance does not pick the one that produces a tidier answer — and a MEDIUM finding can never block a build.
Every verdict is challengeable. Report it, and the outcome is published — including when we were wrong.
The "we were wrong" processOne licence can produce several findings. They are grouped by dependency id, not by scan order.