A new approach to fighting cross-session tracking: multi-layer online fingerprint obfuscation. Spoofs browser/OS (headers & JS), hardware, TLS cipher-suite, canvas, peripherals and much more.
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 100%
Response Time: -
First Timer Success: -
un-nf/404 has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in un-nf/404 respond to incoming external pull requests in approximately 0.0 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 47.9 places un-nf/404 in the B tier.
The external contributor pull request merge rate for un-nf/404 is 100.0%, based on public PR activity from non-core contributors.
un-nf/404 currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Rust project in un-nf/404 welcoming community pull requests and bug fixes.
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/un-nf/404?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (45% approval). Keep your diff compact for rapid review.
Issue 43-byte WAsm module can expose fake CPU architecture Context IEEE-754 leaves the sign/payload of a quiet NaN implementation-dependent. A runtime 0/0 commonly produces a negative quiet NaN on x86 (0xFFF8… for f64) and a positive one on ARM (0x7FF8…). JavaScript can inspect the bit through typed arrays, but a spoofing layer can replace those constructors. A tiny WebAssembly function performs the division, reinterprets the f64 as i64, shifts the sign bit, and returns it without relying on page-replaceable typed-array objects. Minimal instruction sequence: local.get 0; local.get 0; f64.div; i64.reinterpret_f64; i64.const 63; i64.shr_u; i32.wrap_i64 The operand must arrive at runtime; V8 can constant-fold literal 0/0 to a canonical NaN and destroy the oracle. Expected Answer How to configure something Why something works the way it does Whether a feature exists How to debug a problem Design rationale Other: Additional Context https://www.clearcotelabs.com/audit/checks/cp
404 Version v2.2.1 Service worker spawn fingerprint protection Currently, a service worker could spawn, do fingerprinting work in the background, and send an opaque blob to the server. That blob would have native fingerprint values. While this is not common fingerprinting practice, as fingerprinting prevention becomes more popular, this will be one of the first attempts to circumvent such tools. Proposed solution Intercept new Worker() and new SharedWorker() in the main thread before the worker spawns. Inject a bootstrap script into the worker's source that patches its scope before fingerprinting code runs. The mechanism would be intercepting the Worker constructor, fetching or reading the worker script, prepending your patches, and creating the worker from a Blob URL with the patched source. Considerations: CSP worker-src may block blob workers, and the interception itself is detectable. Intercept the Worker constructor and inject OffscreenCanvas patches into the worker scope that wou
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 un-nf/404, 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 un-nf/404 acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
un-nf/404 has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 47.9 places un-nf/404 in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, un-nf/404 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 un-nf/404 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.