Framework semantic default
Redis 8 license RSALv2 SSPLv1 AGPLv3 license file scanner allow-list
A scanner sees a different license set than the deployment allow-list expects.
Agent Quick Fix
Repair against the current Redis contract, then keep the change narrow and source-backed.
Product: Redis
Current-contract area: Redis 8 license selection breaks automated compliance policy
Likely root cause: A scanner sees a different license set than the deployment allow-list expects.
Repair direction: Verifier checks behavior across multiple requests/build modes, not merely compilation. Verify required commands/modules and supported patch channel.Symptom
A scanner sees a different license set than the deployment allow-list expects.
Why This Happens
Local code often type-checks under both old and new framework semantics; the failure depends on the installed framework version and current runtime defaults.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Redis 8 license RSALv2 SSPLv1 AGPLv3 license file scanner allow-list
site:redis.io/blog Redis 8 AGPLv3 license RSALv2 SSPLv1
Redis 8 AGPLv3 Redis blog May 2025
Redis is now available under the OSI-approved AGPLv3 open source license May 1 2025 redis.io
https://raw.githubusercontent.com/redis/redis/8.0/LICENSE.txt
https://redis.io/legal/licenses/Source Trail
GitHub source file/reference: