Document network ecosystem identifiers for package registries and CDNs #7417
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 existing ecosystem domain system (
python,node,go,containers, etc.) already includes all major package registries and CDNs, but lacked documentation and practical examples. Users experiencing firewall denials didn't know how to properly configure network allowlists.New Documentation
Network Configuration Guide (
docs/src/content/docs/guides/network-configuration.md):gh aw logsoutputExample Workflows:
examples/network-python-project.md- PyPI package analysisexamples/network-node-project.md- npm package analysisexamples/network-multi-language.md- Multi-ecosystem projectUsage Pattern
Each ecosystem identifier expands to 5-30 domains. See ecosystem_domains.json for complete domain lists.
Documentation Updates
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.