net/http: remove unused function isLitOrSingle

[austinderek]

TEST

[staging]

HackerOne Code Security Review

🟢 Scan Complete: 1 Issue(s)
🟠 Validation Complete: One or more Issues looked potentially actionable, so this was escalated to our network of engineers for manual review. Once this is complete you'll see an update posted.

Here's how the code changes were interpreted and info about the tools used for scanning.

📖 Summary of Changes

No changes were detected in the HTTP pattern handling code. The source file remains unchanged, suggesting stability in the network routing or pattern matching logic for HTTP-related functionality.

File	Summary
src/net/http/pattern.go	No substantive changes were made to this file. The code appears to be identical between the old and new versions.

ℹ️ Issues Detected

NOTE: These may not require action!

Below are unvalidated results from the Analysis Tools that ran during the latest scan for transparency. We investigate each of these for accuracy and relevance before surfacing them as a potential problem.

How will I know if something is a problem?
When validation completes, any concerns that warrant attention prior to merge will be posted as inline comments. These will show up in 2 ways:

• Expert review (most cases): Issues will be posted by experts who manually reviewed and validated them. These are real HackerOne engineers (not bots) reviewing through an integrated IDE-like tool. You can communicate with them like any other reviewer. They'll stay assigned and get notified with commit & comment updates.
• Automatically: In cases where our validation checks have highest confidence the problem is legitimate and urgent. These will include a description of contextual reasoning why & actionable next steps.

File & Line	Issue
src/net/http/pattern.go Line 397	The removal of the isLitOrSingle function could potentially introduce security issues if this function was being used elsewhere in the codebase for validation or security checks. Without seeing the broader context of how this function was used, removing utility functions that distinguish between literal segments and wildcards could affect path matching security logic.

🧰 Analysis tools

• [ ✅ ] HackerOne AI Code Analysis
• [ ✅ ] HackerOne AI Code Validation
• [ ✅ ] semgrep
• [ ✅ ] gosec
• [ ✅ ] bandit

⏱️ Latest scan covered changes up to commit a97c8f4 (latest)