Smart Kubaba · Repository Firewall

Evaluate proxy packages before download.

Match package versions with intelligence and policy to produce PASS, WARN, or BLOCK decisions.

Smart Kubaba Repository Firewall blocked package list
A real product screen showing the proxy repository, package version, and BLOCK status.

Outcome

Turn the proxy repository into a control point.

Request-time evaluation

Evaluate a new package version with vulnerability and policy context before caching and consumption.

Scoped policy decision

Apply organization, project, or repository policy through one evaluation model.

Exception and audit trail

Manage time-bound risk acceptance with reason, reference, task state, and audit records.

Verified scope

Repository Firewall scope verified in the source project

Proxy request evaluation

Evaluate package versions requested from proxy repositories against intelligence and applicable policy.

Request Control

PASS / WARN / BLOCK

Reflect policy outcomes in download behavior and the decision record presented to users.

Download Decision

Central policy scope

Organization, project, and repository rules with priority and scope resolution.

Scope Resolution

Risk acceptance

Time-bound, reasoned, referenced, scoped exceptions with durable tasks and reevaluation.

Risk Exception

Version-level risk view

Filterable package/version evaluations, decision history, and audit records.

Decision History

Current decision inputs

Firewall decisions use OSV vulnerability data and severity/policy rules; malware, license, and namespace-confusion analysis are outside this scope.

Current Boundary

How is a proxy request decided?

Repository Firewall evaluates the requested package version against intelligence and central policy before download.

  1. 01Request the package

    A user or build tool sends a request to the proxy repository.

  2. 02Match the version

    Compare package coordinates with available OSV data.

  3. 03Resolve scope

    Apply organization, project, and repository policies.

  4. 04Produce a decision

    Record the result as PASS, WARN, or BLOCK.

  5. 05Track the action

    Write downloads, exceptions, and reevaluations to the audit trail.

Enterprise

Apply one policy with ownership boundaries.

Central rules resolve by organization, project, and repository scope; roles, access policies, tasks, and audit records show who governs each decision.

Enterprise

Technical evaluation

Evaluate your package flow on Smart Kubaba.

Let’s review your formats, deployment, and security policies together.