Skip to report

Independent analytics for a public GitHub repository

0x727/JNDIExploit

一款用于JNDI注入利用的工具，大量参考/引用了Rogue JNDI项目的代码，支持直接植入内存shell，并集成了常见的bypass 高版本JDK的方式，适用于与自动化工具配合使用。 — view on GitHub · github.com/0x727/JNDIExploit

Language

Java

License

MIT

open source

Created

Oct 2021

Stars

377

Forks

30

Issues

0 open

Updated 21 Sept 2026, 15:30 UTC

33 /100
DORMANT

tracker score 33/100 methodology →

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

Last release

1795 days ago

1.1

Cadence

no stable cadence

1795d gap

PR merge median

n/a

Issue response median

2.6h

Commits / 7d

0

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 2.6hcohort: n/a

PR first review

sample too smallcohort: n/a

PR merge time

sample too smallcohort: n/a

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

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

0

first-time PRs (12 mo)

—

got a response

n=0 scanned

—

were merged

0 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)

stats unavailable of accepted changes · —

— of accepted changes

GitHub could not compute contributor stats for this repo

Verdict: key-person risk unknown. GitHub never computed contributor statistics for this repository (common on very large commit networks), so concentration cannot be measured.

Open-issue backlog

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

open issues & PRs — right now

0

open issues

0

open pull requests

Tracking daily since 21 Sept 2026 — 1 snapshot so far.

0 open

0 issues + 0 PRs · trend builds as daily snapshots accumulate

Fork network & successors

30 forks · 0 with independent momentum

xiaokp7/JNDIExploit — 1★ · last push 1477d ago

stale

0x727/JNDIExploit 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 (no stable cadence)

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

License unchanged · not archived · no rename/transfer

Fewer than 2 releases in 12mo — no gap to measure

Frequently asked answered from live data · FAQPage structured data

These answers regenerate on every snapshot — they never rot.

Is JNDIExploit still maintained?

No clear signs of active maintenance (score 33/100). Last stable release 1.1 1795 days ago, 0 commits in the last full week, PR merge time not measurable (too few merged PRs in the 90d sample). Evidence collected Mon Sep 21 2026.

What license does JNDIExploit use?

See repository — as reported by GitHub.

When was the last JNDIExploit release?

1.1, 1795 days ago. No stable cadence to measure — no releases shipped in the last 12 months.

Is JNDIExploit safe to adopt for a new project in 2026?

On the evidence: no. 0 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

0x727/JNDIExploit

DORMANT · 33/100

ships no stable cadence · PR merge n/a · ★ 377

0x727/JNDIExploit — maintenance verdict & repo intelligence · tracker.git.tools

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

maintenance dormant · 33
[![maintenance](https://tracker.git.tools/badge/0x727/JNDIExploit)](https://tracker.git.tools/0x727/JNDIExploit)

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.