Repository navigation
Handle leading whitespace in BOM detection - #957
Merged
Merged
Conversation
Accept legal whitespace before JSON and XML content when selecting a parser. Keep file detection bounded in memory and preserve rejection of empty or unsupported input. Signed-off-by: jdotc1 <138259519+jdotc1@users.noreply.github.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 11 |
🟢 Coverage 100.00% diff coverage · +0.12% coverage variation
Metric Results Coverage variation ✅ +0.12% coverage variation Diff coverage ✅ 100.00% diff coverage Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (2c410e3) 7872 5917 75.17% Head commit (1a05bfb) 7883 (+11) 5935 (+18) 75.29% (+0.12%) Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#957) 18 18 100.00% Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
nscuro
approved these changes
Oct 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The parser factory rejects valid JSON/XML documents when legal whitespace precedes their first content byte, including after a UTF-8 byte-order marker. File detection also stops after a four-byte prefix, so longer whitespace prefixes cannot be recognized.
Skip only space, tab, CR and LF during format detection, after the optional UTF-8 marker. Continue scanning files through a buffered stream when the initial prefix is whitespace, and reuse the same detection rules for byte arrays and the existing looksLikeCycloneDX heuristic. The original document is passed unchanged to the selected parser. No new dependency or public API is introduced.
Related downstream report: DependencyTrack/dependency-track#4983 . This addresses the parser-library gap; a released library update and downstream adoption are still required before claiming end-to-end Dependency-Track resolution.
Validation:
mvn -B -q -Dtest=BomParserFactoryTest testpassed after the change: 22 tests, 0 failures/errors/skips.git diff --checkpassed once.JDK 25.0.3, Maven 3.9.16; production compilation retains the project's Java 8 release target. No full suite, CI Java-version matrix or downstream Dependency-Track import run was performed. Existing unrelated validation was reused without rerunning.