Source evidence

cannot disable noncing

No unsafe-inline · support · 2025-01-07T13:56:00+00:00

No unsafe-inline plugin evidence original source source API

neutralsentiment

mediumseverity

0.47relevance

2replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 35 rows with source links

14.3% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

fuzzy21 resolved

I’m trying to disable script-src nonce and use unsafe-inline, but I am still getting nonces in the header. Here’s what I did: I set External source csp mode: to none. I turned on Use ‘ unsafe-hashes ‘ for JS event handlers attributes of HTML elements. (Say NO). We have a lot of base rules we setup. Please, read: https://github.com/MocioF/No-unsafe-inline/issues/3 Thank you, that worked.

Commercial Context

Opportunity

multisite and site-portfolio operations

Multisite portfolio governance for governing updates, reporting, and client-safe operations across many WordPress sites

Buyer: agencies, multisite operators, and maintenance teams

Wedge: surface multisite update risk, network drift, reporting gaps, and client-site exceptions

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: cannot disable noncing: users show bugs, setup pain that may indicate a product gap.

Evidence quote: We have a lot of base rules we setup.

Affected feature: bugs

bugs setup

Plugin

API

No unsafe-inline

200 active installs · 11.8K downloads · rating 100.0

content security policy csp multisite security unsafe-inline

Comments

2 shown

Giuseppe 2025-01-07T21:12:00+00:00

Please, read: https://github.com/MocioF/No-unsafe-inline/issues/3

fuzzy21 2025-01-08T14:55:00+00:00

Thank you, that worked.