Skip to report

Independent analytics for a public GitHub repository

0xdea/semgrep-rules

A collection of my Semgrep rules to facilitate vulnerability research. — view on GitHub · semgrep.dev

Language

C

License

MIT

open source

Created

Mar 2022

Stars

874

Forks

91

Issues

5 open

Updated 21 Sept 2026, 11:23 UTC

57 /100
ACTIVELY MAINTAINED

tracker score 57/100 methodology →

Computed from release cadence, responsiveness, backlog trend and contributor depth.

Last release

98 days ago

v2.0.0

Cadence

every 72.6d

on pace

PR merge median

0.0d

Issue response median

13.2h

Commits / 7d

1

Attention vs delivery — is popularity translating into shipping?

The signature question of dependency due diligence. Columns: commits per month (activity). Line: merged pull requests per month (delivery). 12 full months.

attention — commits / month delivery — merged PRs / month stable release

Reading: delivery held at ~0 merged PRs/mo over the last 12 months. No divergence risk — delivery tracks attention.

Responsiveness — vs cohort percentiles

How fast maintainers answer, review and merge — ranked against repos of similar size and age.

Issue first non-author response

median 13.2hcohort: n/a

PR first review

median 8.3hcohort: n/a

PR merge time

median 0.0dcohort: n/a

Bots excluded Sample: 5 merged PRs (90d) / 9 recent issues. Percentile position measured from the left — shorter is faster.

First-contributor funnel — what happens to a newcomer’s PR?

1

first-time PRs (12 mo)

—

got a response

n=4 scanned

—

were merged

1 newcomer candidates

—

returned ≤90d

verified via author history

Verdict: not enough first-time PRs in the sampled window (2026-03-25..2026-06-23) to call this either way — most contributions here come from people already close to the project.

Contributor concentration (12 mo)

top 1 — 99.6% of accepted changes · last commit Aug 2

top 3 — 100% of accepted changes

long tail — 0 further authors

Verdict: high key-person risk. 2 human commit authors in 12 months; top author (0xdea) holds 99.6%, top 3 hold 100%, 1 authors above 1% each.

Open-issue backlog

Open issues and pull requests right now. Trend history builds from daily tracking.

open issues & PRs — right now

5

open issues

2

open pull requests

Tracking daily since 5 Sept 2026 — 2 snapshots so far.

7 open

5 issues + 2 PRs · trend builds as daily snapshots accumulate

Fork network & successors

91 forks · 0 with independent momentum

Harvester57/semgrep-rules — 4★ · last push 83d ago

alive

0xdea/semgrep-rules is upstream — no successor needed (project active). Top forks by stars are all stale (pushes >1y ago). Successor detection activates if the repo goes dormant.

If this repo goes dormant, this section becomes “Where did development continue?” — with evidence labels per fork.

What changed — last 90d

0 stable releases in 90d (median gap 72.6d)

Issue response sits at a 13.2h median — trend builds as daily snapshots accumulate

License unchanged · not archived · no rename/transfer

Max release gap in 12mo: 121d (cadence 72.6d median)

Frequently asked answered from live data · FAQPage structured data

These answers regenerate on every snapshot — they never rot.

Is semgrep-rules still maintained?

Yes — actively (score 57/100). Last stable release v2.0.0 98 days ago, 1 commits in the last full week, median PR merge 0.0d. Evidence collected Mon Sep 21 2026.

What license does semgrep-rules use?

MIT — as reported by GitHub.

When was the last semgrep-rules release?

v2.0.0, 98 days ago. Median gap between stable releases is 72.6 days; 0 stable releases shipped in the last 90 days.

Is semgrep-rules safe to adopt for a new project in 2026?

On the evidence: yes. 2 human authors in 12 months, no fork-succession pressure. Not published to npm — GitHub activity only.

Share & embed — every share is a branded mini-report

Link preview (auto-generated OG card)

tracker.git.tools

0xdea/semgrep-rules

ACTIVELY MAINTAINED · 57/100

ships every 72.6d · PR merge 0.0d · ★ 874

0xdea/semgrep-rules — maintenance verdict & repo intelligence · tracker.git.tools

README badge (live SVG — every embed is a backlink)

maintenance active · 57
[![maintenance](https://tracker.git.tools/badge/0xdea/semgrep-rules)](https://tracker.git.tools/0xdea/semgrep-rules)

Badge states: active · slowing · maintenance-only · dormant — flips automatically; maintainers embed it because it’s honest.

Methodology

Built from the public GitHub API, the npm registry, deps.dev and Hacker News. Known bot accounts are excluded from response and merge metrics. Verdicts are computed from the evidence shown on this page — nothing is scored that you cannot see. Reports refresh daily.