Repository navigation
Content Hygiene 1.4.0 — build 79
Content Hygiene 1.4.0 — build 79
Read-only declared extraction-output provenance for dependency investigations.
What's changed
- Attribute supported inline named captures and unambiguous search-time transform
REGEX, literal FORMAT capture mappings and DELIMS/FIELDS declarations without
compiling or executing customer PCRE. - Show declared source fields, capture numbers and source offsets in expandable
Splunk-native Explorer/Library details and persistent relationship context. - Preserve compact provenance and potential-path qualifications through impact,
required-content reporting and CSV/JSON exports; do not cache patterns or values. - Retain explicit gaps for dynamic names, ambiguous mechanisms, unsupported
syntax, key cleaning, index-time/routing behavior and effective applicability. - Introduce shared-static-v4 coverage while preserving earlier review decisions,
captured baselines and history. Scans never reaffirm a saved decision.
Upgrade and compatibility
Splunk Enterprise 10.2.5 or later, standalone Linux x86-64 search head with
healthy KV Store. Exact representative runtimes tested: 10.2.5, 10.2.8 and 10.4.4.
Run a bounded scan, then a complete scan after upgrading to collect the new
attribution. Investigate expanded coverage before explicitly reaffirming a review.
Validation and limits
- 680 automated checks pass, plus lint/stylelint, types, branding, build and
portable-package checks. Pre-cert AppInspect 4.3.1: zero errors/failures/future
failures, three reviewed warnings and one manifest skip; not Cloud certification. - Fresh bounded/full scans, native catalog/cache and schema comparisons,
targeted Light/Dark UI checks and 22 real CSV/JSON downloads passed. Original
review records and journals stayed unchanged; native appearance was restored. - Two cold page loads in the emulated minimum-version VM reached the existing
20-second inventory-read timeout; warm retries passed without relaxed limits. - Eligible transform examples were present on the 10.2.8 estate; the other two
estates had no eligible shared examples. Non-default inline source clauses and
new field-specific saved-review rendering use synthetic contracts; native
existing/empty Library states were tested without creating review decisions. - Declared names are not proof of regex validity, matching, field availability,
effective props precedence, runtime use or safe removal. Broader #8 coverage
and #9's future-object Retain policy remain open follow-ups. This is not full
accessibility, production-scale or backend-concurrency recertification.
Customer knowledge objects remain read-only. Private reports, lab configuration,
credentials, source maps and macOS metadata are excluded from the release.
SHA-256 for content_hygiene-1.4.0.tar.gz:
63946c830f18d0734c4277c1c8dfbffaa75e43e430458c2c947b884c3777432d
See the compatibility policy
and user guide
for exact scope and investigation guidance. Published earlier release assets
remain unchanged.