SaaS Ranking
Menu

Semgrep

semgrep.dev · Vulnerability management · checked 2026-09-03

48/100DBand D

Rank 5 of 18 in Vulnerability management, where the median is 28.

We measured 12 of 12 criteria for Semgrep on 2026-09-03. We found 6 with a source and did not find 6 at the addresses we checked. That is a transparency score of 48 out of 100, band D.

Overview

Transparency labelsaas-ranking.com

Semgrep

semgrep.dev · Vulnerability management

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
D 48of 100 Rank 5 of 18

Published commitments4 of 9 found

Measured behaviour2 of 3 found

Checked 2026-09-03. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Semgrep has no such document.

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-03.

Show the 8 addresses we checked
  1. https://semgrep.dev/legal/dpa – reached, no match (HTTP 404)
  2. https://semgrep.dev/dpa – reached, no match (HTTP 200)
  3. https://semgrep.dev/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://semgrep.dev/data-processing-agreement – reached, no match (HTTP 200)
  5. https://semgrep.dev/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://semgrep.dev/legal/gdpr – reached, no match (HTTP 404)
  7. https://semgrep.dev/trust/dpa – reached, no match (HTTP 200)
  8. https://semgrep.dev/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-03.

Show the 7 addresses we checked
  1. https://semgrep.dev/legal/subprocessors – reached, no match (HTTP 404)
  2. https://semgrep.dev/subprocessors – reached, no match (HTTP 200)
  3. https://semgrep.dev/sub-processors – reached, no match (HTTP 200)
  4. https://semgrep.dev/legal/sub-processors – reached, no match (HTTP 404)
  5. https://semgrep.dev/trust/subprocessors – reached, no match (HTTP 200)
  6. https://semgrep.dev/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://semgrep.dev/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-03.

Show the 1 address we checked
  1. https://semgrep.dev/ – third-party requests before any interaction: 825-qqz-896.mktoresp.com, ad.doubleclick.net, alb.reddit.com, analytics.twitter.com, api.cr-relay.com, api.vector.co, bat.bing.com, bat.bing.net, bzrcdn.openai.com, cdn.cookielaw.org, cdn.cr-relay.com, cdn.drda.io, cdn.dreamdata.cloud, cdn.jsdelivr.net, cdn.keyplay.io, cdn.metadata.io, cdn.vector.co, cm.g.doubleclick.net, connect.facebook.net, d.adroll.com, dev.visualwebsiteoptimizer.com, dsum-sec.casalemedia.com, eb2.3lift.com, geolocation.onetrust.com, ib.adnxs.com, image2.pubmatic.com, intent.keyplay.io, ml314.com, munchkin.marketo.net, pages.semgrep.com, pixel-config.reddit.com, pixel.rubiconproject.com, pixel.tapad.com, ps.eyeota.net, px.ads.linkedin.com, region1.analytics.google.com, res.cloudinary.com, s.adroll.com, script.crazyegg.com, snap.licdn.com, static.ads-twitter.com, stats.g.doubleclick.net, sync.outbrain.com, sync.taboola.com, t.co, us-u.openx.net, visitor.reactful.com, www.facebook.com, www.google-analytics.com, www.google.com, www.google.de, www.googletagmanager.com, www.redditstatic.com, x.bidswitch.net

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-03.

Show the 8 addresses we checked
  1. https://semgrep.dev/legal/subprocessors – reached, no match (HTTP 404)
  2. https://semgrep.dev/subprocessors – reached, no match (HTTP 200)
  3. https://semgrep.dev/sub-processors – reached, no match (HTTP 200)
  4. https://semgrep.dev/legal/dpa – reached, no match (HTTP 404)
  5. https://semgrep.dev/dpa – reached, no match (HTTP 200)
  6. https://semgrep.dev/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://semgrep.dev/trust/subprocessors – reached, no match (HTTP 200)
  8. https://semgrep.dev/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-03.

Show the 6 addresses we checked
  1. https://semgrep.dev/legal/sla – reached, no match (HTTP 404)
  2. https://semgrep.dev/sla – reached, no match (HTTP 200)
  3. https://semgrep.dev/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://semgrep.dev/trust/sla – reached, no match (HTTP 200)
  5. https://semgrep.dev/uptime – reached, no match (HTTP 200)
  6. https://semgrep.dev/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://semgrep.dev/legal/privacy/ · checked 2026-09-03

Show the 7 addresses we checked
  1. https://semgrep.dev/legal/privacy – found, but behind a sign-in
  2. https://semgrep.dev/privacy – found, but behind a sign-in
  3. https://semgrep.dev/privacy-policy – reached, no match (HTTP 404)
  4. https://semgrep.dev/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://semgrep.dev/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://semgrep.dev/trust/privacy – reached, no match (HTTP 200)
  7. https://semgrep.dev/datenschutz – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 6
✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://semgrep.dev/legal/privacy/ · checked 2026-09-03

✓

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.semgrep.dev/ · checked 2026-09-03

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://semgrep.dev/pricing/ · checked 2026-09-03

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://semgrep.dev/ · checked 2026-09-03

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://trust.semgrep.dev/ · checked 2026-09-03

✓

security.txt (RFC 9116)

weight 1 of 3

Served at /.well-known/security.txt.

Source: https://semgrep.dev/.well-known/security.txt · checked 2026-09-03

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare