pixellint

Core checks validate URLs, request captures, and consent signals.

Core checks validate URLs, JSON syntax, HTTP request captures, and IAB consent signals. Vendor packs add destination contracts to matching artifacts. A URL has to parse, a network scheme has to be http or https, and a consent parameter has to contain a consent string rather than a placeholder.

Base64 is a permissive alphabet. gdpr_consent=1 and gdpr_consent=true both pass a character check. Decoding the TC String version, the US Privacy version digit, and the GPP header type is what separates a string from a signal.

Request captures and HAR imports retain observed transport evidence and explicit capture uncertainty. A missing original body or redacted header leaves dependent checks unvalidated. Information findings identify that limit while observed endpoint, method, and other available fields still receive their checks.

gdpr_consent=1 is not a TC String

The first six bits of a TCF v2 string are the version, and they have to read 2. A one-character placeholder decodes as something else, or as a truncated core segment. A TCF v1 string decodes as version 1 and is reported as sunset rather than as malformed.

Rule: core.privacy.tc_string_version

A TC String in gpp is the wrong parameter

GPP header type is fixed to 3. A TC String pasted into gpp decodes to header type 2. That is the commonest way to get this wrong: the right string, the wrong field.

Rule: core.privacy.gpp_header_type

Unavailable capture fields keep dependent checks unvalidated.

A HAR export can omit credentials or original body bytes. Explicit request metadata can also mark fields unavailable or redacted. capture_incomplete records this uncertainty. It does not turn an omitted credential into an observed authentication failure, or claim that a destination accepted the request.

Rule: core.request.capture_incomplete

Explicit wire bytes let local checks inspect gzip bodies.

body_base64 records original bytes using standard padded Base64. With one observed gzip Content-Encoding, Pixellint checks framing and integrity before inspecting the decoded text. A raw text body marked gzip, an unsupported encoding, or an opaque non-JSON binary body retains an information finding. Local inspection bounds also leave payload checks unvalidated when they are exceeded.

Rule: core.request.unsupported_body_encoding

What this pack matches

Vendor docs
url.spec.whatwg.org/

Rules

Codes are stable. A finding in CI, MCP, or the playground lands on the same id.

Field Required What it checks Rule ids Source
URL parse and host required The artifact parses as an absolute URL and carries a host. core.url.invalid
core.url.host_missing
docs
http or https required Network-delivered artifacts use http or https. core.url.unsupported_scheme docs
No userinfo, no fragment optional Embedded credentials are deprecated. Fragments never reach the server. core.url.userinfo_deprecated
core.url.fragment_ignored
docs
HTTPS baseline recommended Plain http endpoints are flagged for upgrade. core.url.insecure_transport
JSON parse required A JSON body parses, and the finding names the byte where it stops. core.json.parse_error docs
HTTP envelope, method, and headers required An explicit request capture has a supported envelope. Its method and header names use HTTP tokens, and observed header values contain no forbidden control characters. Destination method and authentication requirements belong to matching vendor packs. core.request.invalid_envelope
core.request.invalid_method
core.request.invalid_header
docs
Capture availability optional Declared unavailable or redacted capture fields produce information findings. Checks that depend on those fields remain unvalidated; observed method, URL, and other fields still run. HAR imports use the same request finding code and preserve their original availability metadata. core.request.capture_incomplete docs
Supported entity representation optional Unsupported or ambiguous content encodings, opaque binary text, and unsupported multipart representations retain information findings. A raw text body marked gzip is not reconstructed into original wire bytes. Explicit body_base64 captures can inspect a single observed gzip encoding locally. Deferred payload checks do not establish destination acceptance or rejection. core.request.unsupported_body_encoding docs
SDK body interpretation scope optional The selected built-in Mixpanel Track, Engage and Groups entries inspect recognized text/plain data= POST bodies only on their exact owning routes. Ambiguous form structure, query/body data conflicts, unsupported charset and the verified paired-CESU-8 producer boundary leave dependent body checks unvalidated. This information finding describes local interpretation scope; original transport evidence and ordinary query checks remain available. Custom and replacement plugins receive no built-in decoder capability. core.request.sdk_body_unvalidated docs
Local SDK body inspection bounds optional The newly admitted SDK plain-text form path bounds entity and decoded text, JSON structure, concrete paths, projected finding text, and evaluation work before dependent payload checks run. Exceeding a local bound produces information and defers those checks. These limits are evaluator policy, not Mixpanel acceptance quotas, and do not retroactively change the legacy raw-JSON or ordinary-form paths. core.request.sdk_body_limit docs
Explicit binary entity integrity optional body_base64 uses canonical standard Base64 with required padding and no whitespace. A supported gzip entity must have valid framing, compressed data, checksum, size, and complete members without trailing junk. Captured JSON and NDJSON entities must decode to UTF-8. Opaque non-JSON bytes remain outside local text inspection instead of receiving a JSON encoding error. core.request.invalid_base64_body
core.request.invalid_gzip_body
core.request.invalid_body_utf8
docs
Local binary inspection bounds optional Binary inspection stops at local bounds of 16 MiB wire bytes, 16 MiB decoded bytes, 1,024 gzip members, and 64 KiB aggregate header bytes per member. Exceeding a local bound produces an information finding and leaves dependent payload checks unvalidated. These bounds are local evaluator policy, not destination quotas. core.request.body_decode_limit docs
Multipart framing optional An observed multipart/form-data body has a valid boundary and supported part framing. File-bearing or otherwise unsupported representations are deferred through unsupported_body_encoding rather than treated as established destination errors. core.request.invalid_multipart docs
NDJSON line syntax optional Every nonempty line of an observed application/x-ndjson body parses as JSON before destination payload checks run. core.request.invalid_ndjson docs
Macros optional A fired URL carries no unresolved macros, including %%NAME%%, !!NAME!!, and [%NAME%]. Macros never sit in scheme, authority, host, port, or userinfo. A pixel URL uses one syntax. A VAST tracker may carry IAB [MACRO] beside ${MACRO}. On vast artifacts, [TOKEN] is checked against the IAB table. core.macro.unexpanded_in_fired_url
core.macro.unsafe_position
core.macro.mixed_syntax
core.macro.broken_delimiter
core.macro.vast_unknown
core.macro.vast_lowercase
core.macro.vast_deprecated
TC String optional gdpr is 0 or 1. A TC String is decoded, not alphabet-checked. Version 2, core segment long enough, not a placeholder. core.privacy.gdpr_invalid
core.privacy.gdpr_consent_missing
core.privacy.gdpr_consent_without_flag
core.privacy.gdpr_consent_ignored
core.privacy.gdpr_consent_malformed
core.privacy.tc_string_version
core.privacy.tc_string_truncated
docs
GPP and US Privacy optional GPP header type is 3. A TC String in gpp is type 2. US Privacy is a version digit plus three Y/N/- characters, and is deprecated. core.privacy.gpp_malformed
core.privacy.gpp_sid_missing
core.privacy.gpp_sid_malformed
core.privacy.gpp_header_type
core.privacy.gpp_header_version
core.privacy.us_privacy_malformed
core.privacy.us_privacy_deprecated
core.privacy.us_privacy_version
core.privacy.duplicate_signal
docs

Validate a payload

pixellint validate url "$ARTIFACT" --rulepack core

Try this failing payload in the playground. gdpr_consent=1 is not a TC String.

https://example.com/px?id=1&gdpr=1&gdpr_consent=1

cargo install pixellint · npm install pixellint