RepoPilot

vercel / swr

Search vercel/swr

GitHub

Repository health

Security advisories, maintenance activity, dependencies and license for vercel/swr, with what was checked and what was not.

Security

0
Critical
0 direct
0
High
0 direct
0
Moderate
0
Low

25 dependencies checked (25 direct), npm, via deps.dev. Findings apply only to the packages and versions checked.

OpenSSF Scorecard · 5.7/10

Checks sorted from strongest to weakest.

  • Maintained15 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1010/10
  • Security-Policysecurity policy file detected10/10
  • Dangerous-Workflowno dangerous workflow patterns detected10/10
  • Binary-Artifactsno binaries found in the repo10/10
  • Licenselicense file detected10/10
  • Code-ReviewFound 19/30 approved changesets -- score normalized to 66/10
  • Token-Permissionsdetected GitHub workflow tokens with excessive permissions0/10
  • Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 00/10
  • CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected0/10
  • Fuzzingproject is not fuzzed0/10
  • SASTSAST tool is not run on all commits -- score normalized to 00/10
  • Packagingpackaging workflow not detectednot scored
  • Branch-ProtectionScorecard could not run this check.not scored
  • Signed-Releasesno releases foundnot scored

Maintenance

22 Sept 2026
Last commit
active
100
Commits / year
32
Contributors
recent window
v2.6.0-beta.0
Latest release
~33d cadence

Outside contributions: 6 of 70 external pull requests merged (23% of those decided), median 5 days to merge.From the 100 most recently updated pull requests, bots excluded.

Recent releases

Commit activity

100 commits sampled
May
Aug
Nov
Jan '25
Feb
May
Aug
Nov
Jan '26
Feb
May
Aug

Click a bar to browse commits — or open GitHub for the full month ↓

Work rhythm

Commits by day of week

Pull request health

Resolution rate0%
Median time to merge/close: 6.6d · last 11 PRs

How fast do PRs resolve?

< 1d
4
1–3d
0
4–7d
2
1–4w
0
> 1mo
5

Days from open to merged / closed, last 11 PRs.

Pending right now19 open PRs

Recently merged4 PRs in the recent window

Issue triage — last 12 weeks

Blue bars = issues opened that week, green = closed. Healthy projects keep these roughly in balance — a persistently bigger blue bar means an opening backlog. open issues on GitHub ↗

Release cadence· median 17d between releases

Actively shipping

Latest v2.6.0-beta.0 shipped 22d ago · typical gap 17d · shipping faster than before · 10 releases sampled.

all releases on GitHub ↗

New faces — last 90 days5 contributors appearing for the first time in this window

Heuristic: contributors whose earliest commit in the recent sample is < 90 days old AND who have ≤ 3 commits in the window. Click a name for their commits in this repo.

Top contributors

Issue health

Computed from GitHub Issues — no estimates. Per-issue rates use the 13 most-recently-updated issues (recent, not all-time); the open total and oldest-open age are repo-wide.

Open issues232

Total open on the repo (authoritative).

Median time to close2mo

From 4 recently-closed issues. p90 1.5y.

Oldest open issue—

Age of the longest-open unresolved issue.

Awaiting first reply11%

1 of 9 recent open issues have no comments yet.

Stale backlog78%

7 of 9 recent open issues had no update in 30d+.

Triage gap78%

7 of 9 recent open issues are unlabeled.

What the backlog is about

AI-generated

Open issues grouped into themes by an LLM from their titles — a summary, not an authoritative classification. Numbers reflect the 9 most-recently-active open issues.

Most-wanted

Open issues with the most positive reactions — what the community is asking for.

Most-discussed

Open issues with the most comments — where the conversation is.

Labels in the recent sample

reproduction needed1RFC1bug1improvement1

Per-issue rates are computed from a sample of 13 most-recently-updated issues, so they describe recent behavior rather than the all-time backlog. Reaction and comment counts come straight from GitHub.

Dependencies

Checked packages and import counts

Checked counts describe advisory coverage, not the repository’s complete dependency inventory. External imports come from a separate source-code graph.

25
Packages checked
npm
25
Direct packages checked
checked count, not total dependencies
0
Transitive packages checked
checked count, not total dependencies
Unknown
External imports
distinct modules in the captured graph

License

MIT
License
Permissive
Family
Unknown
Dep conflicts
No dependency license scan coverage
Commercial use: Generally fine for commercial and proprietary use, subject to attribution and notice terms.