Home›Services›Open-source intake

Only approved open-source components reach your builds

Every build pulls packages and images from the internet. Commercial repository firewalls put new ones in quarantine until security has looked at them. We build the same control on open tools: images are scanned and blocked in Harbor, packages enter your internal registry only through an approved merge request, and everything approved keeps being watched.

from $6,000 · fixed price Measured first, then fixed price and dates Every decision on record
The problem

New dependencies arrive in builds without anyone from security seeing them.

What we build

Quarantine for images, an approval flow for packages, monitoring after approval.

The result

Builds use only approved components; every decision has a reviewer and a date.

Is this you?

How vendor firewalls do it

So you know what the commercial benchmark is:

Compared with vendor firewalls

Same goal — nothing new enters builds without a check — reached with open, generally available tools.

Commercial firewallSonatype Repository Firewall, JFrog Curation
Open toolsHarbor, GitLab, open scanners
Quarantine of new imagesin the proxy repository
Harbor proxy projectscan on arrival; pull blocked above your severity threshold3
Unsigned imagespolicy
Harbor content trustunsigned images cannot be pulled3
Quarantine of new packagesnpm, PyPI, Maven
Approval merge requestchecked by pipeline, approved by security, then published
Malicious-package detectionvendor threat data
GuardDog + vulnerability scanopen heuristics, YARA rules
Waiversin the vendor console
CVE allow-list / MR exceptionwith owner and expiry
Continuous monitoringof what was let in
Dependency-Trackalerts on new vulnerabilities

How it works for packages

What you get

Image quarantine

Harbor proxy projects that scan every new image and refuse to serve those above your severity threshold or unsigned.

Package approval flow

Allow-list project, check pipeline and publishing into your internal registry, ready for the first requests.

Exception process

How a developer asks for an exception, who decides, and when the exception expires.

Monitoring

Dependency-Track fed with everything approved; alerts to the owners of affected projects.

Runbook and guide

One page for developers (how to request a package), one for security (how to review).

How it goes

The order is always the same. How long each step takes depends on your volume — the measurement in step 1 sets the price and the dates. Our free scope script gives the first numbers.

  1. Step 1 · 1–3 days

    Measure

    What your builds pull today, from where, and how often new dependencies appear. Fixed price and plan.

  2. Step 2

    Images

    Harbor proxy projects with scanning and blocking; builds re-pointed.

  3. Step 3

    Packages

    Allow-list, check pipeline, internal registry; pilot team first.

  4. Step 4

    Monitoring and handover

    Dependency-Track, exception process, guides, sessions for developers and security.

What we need from you

  • A named owner in security who will approve requests.
  • Network control for CI runners (we tell you what to close).
  • One pilot team willing to work through the new flow first.

Not included

  • Reviewing packages on your behalf — the decision stays with your security team.
  • Guarantees that no malicious package ever gets through: checks reduce risk, they do not remove it.
  • Buying commercial threat-intelligence feeds.
from $6,000

Fixed price after the measurement in step 1. Paid by milestone.

What changes the price

  • Formats — containers only, or also npm, PyPI, Maven and others.
  • Number of build pipelines to re-point.
  • Existing tools — Harbor, Nexus CE or GitLab registries already in place.

Often combined with a DevSecOps Pipeline on GitLab or a Nexus CE clean-up.

Questions teams ask

Won't this slow developers down?

For images, no: scanning happens in the proxy. For packages, a new dependency waits for an approval. We agree a response time with security and pre-approve common, well-known packages so the queue stays short.

Is this as good as Sonatype Repository Firewall or JFrog Curation?

Those products bring their own threat data and transparent quarantine for packages. Our set-up uses open scanners and an explicit approval step instead. For many teams that is enough; for others the commercial product is worth its price — we tell you which after the measurement.

Can we keep Nexus Community Edition?

Yes. Nexus CE can host the approved packages; we add the approval flow and the image quarantine around it.

Do we need GitLab Premium?

No. Premium makes approvals by the security group enforceable in one project; on Free we use a separate allow-list project that only security can merge into.

Often done together

Tell us what your builds pull from the internet

Formats and number of pipelines — enough for a price range on a 30-minute call.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Sources — public announcements, documentation and legal texts, for orientation only; not legal advice. Sonatype Repository Firewall is a trademark of Sonatype; JFrog Curation is a trademark of JFrog.
  1. Sonatype Help: Firewall Quarantine
  2. JFrog Docs: Manage Curation
  3. Harbor Docs: Project configuration
  4. Datadog Security Labs: GuardDog 2.0 release
  5. GitLab Docs: Merge request approval rules
Book a 30-minute call