llms.txt
Compare with other sites' llms.txt files →# Bytesafe
Bytesafe is a software supply chain security and transparency platform from Bitfront AB. It has three products:
- Dependency Firewall (/firewall): blocks vulnerable, malicious and policy-violating open source packages before they reach developers, CI/CD pipelines and AI agents. It sits in front of your existing package registry (JFrog Artifactory, Sonatype Nexus, GitLab, GitHub Packages, Azure Artifacts) and evaluates every package request against your policy.
- Trust Repository (/trust): collects SBOM, VEX and end-of-life documents from your suppliers, and publishes your own to your customers. Pricing on request.
- SBOM Observer (/observer): analyzes SBOMs from your builds and suppliers for vulnerabilities, licenses and policy violations, enforces policy in CI/CD and keeps evidence per release.
- Company: Bytesafe (Bitfront AB), EU-based, Sweden. Software supply chain security since 2018.
- Hosting: EU data residency.
- Dependency Firewall deployment: Cloud (SaaS), Managed Cloud, BYO Cloud, On-Premise.
- Dependency Firewall ecosystems: npm, PyPI, Maven, NuGet, Go, Composer, Cargo, RubyGems, Conda, Containers (OCI). Current status and coverage per ecosystem: docs.bytesafe.dev/firewall/ecosystems.
- Dependency Firewall pricing: usage-based on three meters. Active users, packages scanned and downloads served. The largest sets the price, the other two are included at the same size. From EUR 99 / month.
- SBOM Observer pricing: Business EUR 69 per user per month for small teams, Enterprise by quote for 25+ users. No trial plan; a live demo and a free SBOM Analyzer need no signup.
- Docs: docs.bytesafe.dev/firewall for Dependency Firewall, docs.bytesafe.dev/observer for SBOM Observer.
## Dependency Firewall
### Core capabilities
- Policy engine: rules by package name, version range, age, license, CVSS/EPSS severity, provenance.
- Vulnerability blocking: block packages with known CVEs before install. CVSS and EPSS thresholds per team or registry.
- Malware scanning: block known malicious packages using dedicated malware databases (separate from vulnerability feeds).
- Safety delay: hold newly published versions for a window you configure so the ecosystem has time to surface zero-day issues.
- Dependency confusion protection: internal packages always resolve from your private registry.
- Trust downgrade detection: flags npm releases published with weaker provenance than the version before them, the pattern behind account-takeover attacks. npm only today.
- Publish scanning: scan packages for malware, secrets and sensitive data before upload to an upstream registry.
- Audit log: every block, allow and exception recorded and exportable to SIEM.
- Live decision logs: package, version, requester, rule and outcome visible to developers and security teams.
- Exception workflow (waivers): developers request an exception from the blocked install, and the team you choose approves, edits or denies it. Exceptions carry a reason and expire automatically.
- Policy as code: configuration in Git. API-driven.
### How it works
1. Route CI/CD pipelines and developer tooling at Dependency Firewall instead of public registries directly.
2. Define rules: vulnerability thresholds, malware scanning, safety delays, allowlist/blocklist. Multiple firewalls per environment or team.
3. Every package request is evaluated in real time. Blocked packages are logged with the rule that triggered. Approved packages are served transparently.
No agent installs. No workflow changes. Standard package managers (npm, bun, yarn, mvn, pip, nuget) keep working. Only the registry URL changes.
## Pages
- /firewall: product overview. The four lead rules, supported ecosystems and integrations, guides, FAQ.
- /firewall/features/release-delay: hold newly published versions for a window you set. How version filtering works and where pinned versions fail.
- /firewall/features/malware-blocking: malware rules on download and publish, with confidence and effort settings.
- /firewall/features/vulnerability-blocking: a vulnerability rule with a maximum CVSS and a maximum EPSS score. A vulnerability has to exceed both, scores are read on every request, and the rule can log before it blocks.
- /firewall/features/license-enforcement: license sets (named lists of SPDX license IDs, shared across firewalls) and the rule that blocks downloads against them.
- /firewall/features/dependency-confusion: internal upstreams and a rule that reserves internal package names.
- /firewall/features/central-rules: one baseline firewall per ecosystem, whose rules every team, CI and agent firewall of that ecosystem inherits.
- /firewall/features/web-proxy: web proxy chaining. A company web proxy such as Zscaler, Prisma Access or Squid forwards registry traffic to the firewall, so every machine behind it is covered with no setup per machine.
- /firewall/features/exception-workflow: the waiver workflow. Developers request an exception from the blocked install, and the team you choose approves, edits or denies it with a comment. Requests and decisions are in the audit log and sent as webhook events.
- /firewall/features/container-firewalling: how rules apply to Docker and OCI images. OS package vulnerabilities, malware and secrets scanning per layer.
- /blog: guides and updates. AI coding agents and dependency policies, Docker and OCI firewalling, delaying new versions without breaking builds.
- /observer: SBOM Observer. SBOM management, vulnerability matching against OSV, GitHub Advisories and NVD, VEX review, policies in CI/CD, container SBOMs by layer, evidence per release for CRA, NIS2 and DORA.
- /observer/sbom-analyzer: free SBOM Analyzer. Upload one CycloneDX or SPDX file, no signup.
- /pricing/observer: SBOM Observer Business and Enterprise plans.
- /trust: Trust Repository. Collect SBOM, VEX and lifecycle documents from suppliers, and publish your own to customers and partners. The same record is what you share with regulators.
- /firewall/container-dependency-firewall: container and OCI image firewalling. Layer scanning for malware and secrets, OS package vulnerability matching from apk, dpkg and rpm databases, and per-image build step and base image analysis.
- /firewall-next-gen: what is new in the current Dependency Firewall compared with the previous generation, plus migration information for existing customers.
- /how-dependency-firewall-works: architecture, what is checked on every request, how decisions are logged.
- /pricing: Dependency Firewall Cloud and Enterprise plans, add-ons, comparison.
- /about: company background.
- /use-cases: specific scenarios, grouped by product. Dependency Firewall: malicious packages, vulnerable dependencies, CI/CD protection, AI coding agents, policy governance. Each use case lists the features that reach its goal. SBOM Observer: SBOM management, vulnerability impact, regulatory compliance, software inventory, M&A due diligence.
- /what-is-a-dependency-firewall: product-anchored explainer covering the definition, where the firewall sits, a comparison with SCA scanners and repository managers, checks that work without a CVE, and how Bytesafe implements it.
- /security: deployment options (managed SaaS, BYO Cloud, on-premise, partner/MSP), data residency, DPA, who operates it.
- /contact: get in touch.
## Reference content
- [llms-full.txt](https://bytesafe.dev/llms-full.txt): full curated content for all pages above, single file.
- [sitemap.xml](https://bytesafe.dev/sitemap.xml): machine-readable list of all pages.