Skip to report

Independent analytics for a public GitHub repository

1229984599/nav

个人导航网站 — view on GitHub · github.com/1229984599/nav

Language

Vue

License

MIT

open source

Created

Jul 2023

Stars

383

Forks

17

Issues

4 open

Updated 21 Sept 2026, 15:31 UTC

38 /100
SLOWING

tracker score 38/100 methodology →

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

Last release

187 days ago

v1.1.6

Cadence

every 1.9d

187d gap

PR merge median

n/a

Issue response median

9.6h

Commits / 7d

—

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 9.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) / 2 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)

top 1 — 76.5% of accepted changes · last commit Mar 15

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 (1229984599) holds 76.5%, top 3 hold 100%, 2 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

4

open issues

0

open pull requests

First snapshot taken today — trend lines fill in as daily snapshots accumulate.

4 open

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

Fork network & successors

17 forks · 0 with independent momentum

91xxn/nav — 0★ · last push 917d ago

stale

1229984599/nav 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 1.9d)

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

License unchanged · not archived · no rename/transfer

Max release gap in 12mo: 6d (cadence 1.9d median)

Frequently asked answered from live data · FAQPage structured data

These answers regenerate on every snapshot — they never rot.

Is nav still maintained?

Partially — activity is slowing (score 38/100). Last stable release v1.1.6 187 days ago, commit stats unavailable (GitHub never computed them), PR merge time not measurable (too few merged PRs in the 90d sample). Evidence collected Mon Sep 21 2026.

What license does nav use?

See repository — as reported by GitHub.

When was the last nav release?

v1.1.6, 187 days ago. Median gap between stable releases is 1.9 days; 0 stable releases shipped in the last 90 days — the current 187d gap is well above that median.

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

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

1229984599/nav

SLOWING · 38/100

ships every 1.9d · PR merge n/a · ★ 383

1229984599/nav — maintenance verdict & repo intelligence · tracker.git.tools

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

maintenance slowing · 38
[![maintenance](https://tracker.git.tools/badge/1229984599/nav)](https://tracker.git.tools/1229984599/nav)

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.