Copy/paste detector for source code. 220+ languages, Rust engine, SARIF/HTML/badge reporters, GitHub Action, MCP server for AI agents.
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 49%
Response Time: 22h
First Timer Success: 80%
kucherenko/jscpd has a recorded first-timer success rate of 80.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kucherenko/jscpd respond to incoming external pull requests in approximately 22.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 64.2 places kucherenko/jscpd in the A tier.
The external contributor pull request merge rate for kucherenko/jscpd is 48.6%, based on public PR activity from non-core contributors.
kucherenko/jscpd currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Established TypeScript ecosystem in kucherenko/jscpd. Maintains structured code review standards for external contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/kucherenko/jscpd?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~15 hours (61% approval). Large PRs (>500 lines) take ~108 hours (22% approval). Keep your diff compact for rapid review.
Summary Tracking issue for upstream work in the linter aggregators that bundle jscpd: default them to new-duplication gating instead of threshold: 0, fix the parallel report-path race, and confirm the linux/arm64 npm binary. Why Super Linter runs jscpd by default with threshold: 0; MegaLinter does the same. This is the most common reason projects set VALIDATE_JSCPD: false (survey in #994; Stack Overflow 77348258; kirodotdev/KiroCrew#6439 "every PR red on an unrelated clone"). oxsecurity/megalinter#2450 (open since 2023) asks MegaLinter to stop enforcing 0% unintentionally. oxsecurity/megalinter#3979 (open, 17 comments): race on jscpd-report.json when linters run in parallel — a stable, configurable report path (--output per invocation, or --report-name) would resolve it. super-linter#5541 (closed "not planned"): VALIDATE_ALL_CODEBASE: false is ignored by jscpd because it needs the whole tree — --baseline-from-ref is now the correct answer and should be the documented one. MegaLint
Summary Documentation recipes (and, where cheap, thin plugins) for running jscpd in Nx, Turborepo and moon, and a danger-js plugin that posts the new-clone summary. Why GitHub code search: 14 turbo.json and 3 Nx project.json files wire jscpd by hand with different conventions (per-package vs root, cache inputs unspecified, so Turbo either never caches or caches stale results). Several 2026 TypeScript starter templates bundle jscpd in a "quality gate" next to knip, oxlint/biome and dependency-cruiser; a canonical recipe keeps them consistent with --skip-isolated and --baseline-from-ref. Danger: only elpassion/danger-py-jscpd (Python, 2020) exists; nothing for danger-js. Proposal docs/monorepos.md: root-level run with --skip-isolated groups vs per-package runs; Turborepo task definition with correct inputs/outputs for the report directory; Nx target with dependsOn and cache settings; moon task; pnpm --filter patterns; how --baseline-from-ref fits affected workflows. danger-plugin-jscp
Summary Suppress the tips/sponsor line automatically when stdout is not a terminal (CI logs, pipes, agent hooks), without requiring --no-tips. Why #788 side complaint: "NEVER put garbage in console output" — the run was inside a CI job. The ai reporter docs already recommend --no-tips; agents and hooks that forget it pay tokens for it. AI-hook articles (PHP Architect, Aug 2026) pass --no-tips on every invocation. Common convention (npm, cargo, Homebrew): promotional/interactive hints only on a TTY. Proposal Print tips only when stdout is a TTY and --no-tips is absent; also honor CI=true, NO_COLOR and a JSCPD_NO_TIPS=1 environment variable. Keep --no-tips for explicitness. Good first issue for a contributor. Related #788, #871. Context: September 2026 research pass over jscpd issues, external repositories that use jscpd, and ~30 competing clone detectors. Sibling issues from the same pass are collected in the roadmap issue (linked in a comment below).
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to kucherenko/jscpd, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of kucherenko/jscpd acknowledge new external contributions in approximately 22 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 48.6% were successfully merged into the primary branch.
kucherenko/jscpd has a recorded first-timer success rate of 80.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~22 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 64.2 places kucherenko/jscpd in the Welcoming tier.
The external pull request merge rate is 48.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kucherenko/jscpd currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for kucherenko/jscpd are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.