Features

On-premises controls for your dependencies

Enforce package policy at download time, investigate the decisions it makes, and export the evidence. ShieldedStack runs the proxy, console, and worker on your infrastructure, with policy and audit records in your database.

Secure Package Proxy

A proxy for 10 package ecosystems that sits between developers and package registries. Configure existing package managers to use your endpoint and API key. Container image support is available separately in beta.

  • Apply shared download policy to local development and CI restores.
  • Reuse cached assessments and record the reason behind package decisions.

Proxy Modes: Trust-Then-Verify & Verify-Then-Trust

Choose the security posture that matches your risk tolerance and development velocity.

Trust-Then-Verify

Permit missing evidence while collection runs in the background. Known vulnerability, license, deny-list, and release-age policy violations still block.

Use it for an inventory-first rollout with deliberately chosen policy settings.

Verify-Then-Trust

Block packages until they pass security validation, querying vulnerability and license metadata inline for unknown versions.

Only packages that meet policy requirements are allowed through the proxy.

Package Download Traceability

When a vulnerability is disclosed after a package was allowed through, ShieldedStack helps answer the urgent question: where did this package version actually go?

  • Find requests by package, version, project, timestamp, and client context.
  • Identify the environments and CI runners that requested an affected version.
  • Inspect the matched rule as it stood when the decision was recorded.
  • Review before-and-after policy changes and export the evidence.

Explore the decision and policy audit trail →

Blocked Maven request showing its decision reason, matched deny rule, project, and client context

Policy Engine

Decide which dependencies each workspace can install, with explicit overrides and an explainable decision for recorded requests.

  • Approved catalogues: Require allow-list membership per ecosystem or across the workspace. Explicit allow matches override later checks.
  • Vulnerability thresholds: Set a minimum severity or CVSS score for blocking.
  • License enforcement: Deny SPDX identifiers with expression-aware evaluation of dual licenses.
  • Release grace periods: Hold back newly published versions until they reach your minimum age.
  • Reviewable exceptions: Accept one advisory on an exact version, with a reason and optional expiry.

Explore policy precedence, evidence, and exceptions →

Security Policy settings showing allow and deny controls, per-ecosystem allow-list requirements, Verify Then Trust, a High severity threshold, and a seven-day release grace period

Package Filter Rules & Policy Portability

Manage allow and deny rules in one searchable workspace table. Prepare and review rules before enabling enforcement.

  • Scope rules by ecosystem, package pattern, and version range.
  • Record reasons and expiry dates for temporary allowances.
  • Check which allow or deny rule matches before applying a change.
  • Validate, import, and export rule sets as JSON between workspaces.
Package Filters showing allow and deny patterns, ecosystem and status filters, version ranges, reasons, expiry dates, and check, export and import controls

Container Image Policy - Beta

Evaluate pulls from Docker Hub, GHCR, Quay, MCR, Chainguard, and Docker Hardened Images using known vulnerabilities in a trusted publisher’s signed SBOM. Approve platform digests, inspect image contents, and require an approved catalogue just for images.

Images without a trusted signed SBOM are blocked in either mode unless an allow rule admits them. Container policy does not apply license checks or release grace periods.

Explore signed-SBOM checks and image policy →

Package Scanner

Bring existing repositories and CI jobs into your inventory, including projects that restore outside the proxy.

  • Read manifests and lockfiles across 11 package ecosystems, including SwiftPM.
  • Run locally or schedule inventory uploads from CI.
  • Use the collected inventory for assessment, alerts, and SBOM exports.

Explore lockfile coverage and CI inventory →

Real-Time CVE Alerts

Continuous vulnerability intelligence monitors your dependency inventory and raises alerts when new advisories affect package versions in use.

  • Event-driven enrichment updates package intelligence after new vulnerability disclosures.
  • An aggregated alert feed surfaces CVEs affecting your inventory in one prioritized view.
  • Severity filtering and acknowledgement workflows support security triage.
  • Configurable cooldowns reduce repeated advisory alerts.
  • Affected versions, first patched versions, plain-language guidance, and ecosystem-specific upgrade commands support remediation.
ShieldedStack CVE alert dashboard with vulnerability notifications and severity indicators

License Change Detection

Track license changes across package versions to catch compliance risks before they affect your organization.

  • Compare a newly tracked release’s license with the nearest earlier tracked version; untracked historical releases are not fetched to fill gaps.
  • Alerts for transitions to restrictive or incompatible licenses.
  • SPDX-based license intelligence mapped to business-friendly risk categories.
  • Historical license tracking for audit and compliance reporting.
  • Denied SPDX identifiers are enforced at install time by the policy engine, so a restrictive license blocks the package rather than only raising an alert.

Explore install-time license enforcement →

Connections and Notification Channels

Route alerts from ShieldedStack into your team's existing workflows.

  • Microsoft Teams: Send vulnerability and license-change alerts to dedicated channels.
  • Slack: Post the same alerts into a Slack channel, laid out with severity, advisory, and the version that fixes it.
  • PagerDuty: Page your on-call team, grouping repeat alerts for one advisory onto the open incident.
  • Webhooks: Call other systems when ShieldedStack dispatches a notification.
  • Configure multiple channels per workspace with independent filtering rules.
  • Include severity, affected packages, and direct console links in notification messages.

Set up channels, severity filters, and webhook payloads →

ShieldedStack notification channel configuration

Data Export & SBOM Generation

Export dependency inventories and Software Bills of Materials for compliance, governance, and incident response.

  • SBOM export in CycloneDX or SPDX 2.3 JSON, per project or as an archive of per-project files. Vulnerability data is CycloneDX-only.
  • CSV and JSON exports for custom reporting and GRC integrations.
  • Vulnerability reports with advisory details, severity ratings, and affected package versions.
  • License data and risk classification included in package exports and the license inventory.
  • Streamed CSV exports of decisions and policy changes over a selected period, plus historical settings through the API.

Compare SBOM formats and export coverage →

Risk Scoring & Intelligence

A context-aware risk engine quantifies package safety across security, compliance, and maintainability dimensions.

  • A unified 0-10 risk score blends vulnerability severity, version age, license posture, and maintenance signals.
  • Security, compliance, and maintainability dimensions help teams identify remediation priorities.
  • Repository health metrics highlight engineering maturity and maintenance risks.
  • Each package version is checked against known vulnerabilities and malware, with a score for how likely each is to be exploited.
  • Interactive dashboards surface risky, outdated, and newly vulnerable packages.
ShieldedStack risk scoring dashboard showing package risk scores and vulnerability trends

MCP Server for AI Security Assistants

Connect AI coding agents and security assistants to ShieldedStack through a read-only Model Context Protocol server with workspace-scoped dependency and vulnerability intelligence.

  • Ask which projects use a package or which findings deserve attention first.
  • Search vulnerabilities, risky and outdated packages, and project inventory.
  • Connect to your Portal with a dedicated workspace-read API key.

Explore MCP tools and workspace access →

Collaborative Security Console

A centralized workspace aligns security, platform, and development teams around shared dependency intelligence.

  • Unified package inventory with CVE status and license posture.
  • Self-service policy management for filters, severity and CVSS gates, denied licenses, grace periods, cooldowns, and vulnerability exceptions.
  • Granular API key rotation and environment-specific access controls.
  • Shared dependency-risk visibility for security analysts, platform engineers, and application developers.
  • Guided onboarding and package-manager connection instructions.

Test it on your infrastructure

Use the 30-day on-premises trial to validate your package managers, policies, and operations. Prefer a first look? The separate 7-day hosted Portal evaluation uses synthetic package activity.