Skip to content

Missing crates.io/static.rust-lang.org in Python and Deno ecosystem allowlists #950

@Mossaka

Description

@Mossaka

Summary

Two repos that have Rust-based dependencies fail to build because crates.io and static.rust-lang.org are not in the Python or Deno ecosystem allowlists:

Repo Language Ecosystem What Needs Rust
pydantic Python python pydantic-core is a Rust extension (compiled via maturin/cargo)
jsr Deno node Has a Rust backend API component

Details

  • The rust ecosystem allowlist includes crates.io, static.crates.io, static.rust-lang.org
  • But when a Python or Deno project has Rust dependencies, they use the python or node ecosystem — which doesn't include Rust registry domains
  • These projects need cross-ecosystem domain access

Suggestion

Either:

  1. Add crates.io, static.crates.io, static.rust-lang.org to the python and node ecosystem allowlists
  2. Or allow workflows to specify multiple ecosystems (e.g., network.allowed: [defaults, python, rust])

Note: The workflow markdown already supports listing multiple ecosystems, so the fix for individual workflows is to add rust to their allowed list. But it would be better if the python ecosystem included these by default since many Python packages have Rust extensions (pydantic, orjson, ruff, etc.).

Experiment Context

  • gh-aw: v0.45.2, AWF: v0.19.1
  • Full report: AWF Build/Test Experiment v3 (Feb 17, 2026)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions