PostHog/posthog-js - Open Source PR Review Scorecard

Send usage data from your web app or site to PostHog, with autocapture.

C-Rank Grade: A (Welcoming) - 66/100

External PR Merge Rate: 77%

Response Time: -

First Timer Success: 73%

Frequently Asked Questions

Is PostHog/posthog-js welcoming to first-time open-source contributors?

PostHog/posthog-js has a recorded first-timer success rate of 72.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in PostHog/posthog-js 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.

What does the 65.9 C-Rank™ score (A Tier) represent?

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 65.9 places PostHog/posthog-js in the A tier.

What is the external contributor pull request merge rate for PostHog/posthog-js?

The external contributor pull request merge rate for PostHog/posthog-js is 77.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in PostHog/posthog-js?

PostHog/posthog-js currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

PostHog
PostHog/posthog-jsA•Welcoming633
GitHub
Back to Explorer
PostHog

PostHog/posthog-js

633
Active (30d)A•Welcoming(66/100)TypeScript

Send usage data from your web app or site to PostHog, with autocapture.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
9.1/10
Patience Score
9.0/10
Nitpick Rate
20%

Highly welcoming maintainers in PostHog/posthog-js. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
77.4%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
72.9%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
52 core
Highly collaborative maintainer core
Diagnostic Health HUD
77.4%
Merge Gauge
72.9%
1st-Timer
Community Vibe53/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for PostHog/posthog-js
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/PostHog/posthog-js)](https://getmerged.abhishekco.de/PostHog/posthog-js?utm_source=github&utm_medium=badge)

Active Good First Issues (2)

View on GitHub

Context This is the WeChat Mini Program runtime scope split out of #2223. WeChat Mini Programs do not provide the browser APIs expected by posthog-js or posthog-js-lite. They use platform-specific APIs such as wx.request, wx storage, and Mini Program lifecycle hooks. Proposed scope Provide an officially supported PostHog SDK for the WeChat Mini Program runtime, preferably built on @posthog/core. MVP capabilities Event capture User identification and reset Persistent and session super properties Session tracking Persistent event queue Batching, retries, and explicit flushing using wx.request Persistence using WeChat storage APIs Appropriate flushing during Mini Program lifecycle transitions Out of scope for the initial SDK Browser DOM-based features such as web autocapture, heatmaps, and session replay require separate Mini Program-specific designs and should not be implied by the MVP. Acceptance criteria A supported package is published from this repository Capture, identify, rese

📅 Opened Aug 11, 2026💬 1 comment
Quality: 80/100Contribute

Bug description:** When using posthog-react-native in a bare React Native project (without Expo) with Hermes enabled, the Metro serializer provided by the SDK (createPostHogMetroSerializer) crashes during bundling with: Error: Chunk ID was not found in the bundle. This makes it impossible to upload source maps for error tracking in non-Expo React Native apps. The issue is in three files within the posthog-react-native package: File 1: dist/tooling/utils.js — determineDebugIdFromBundleSource function The SDK generates a code snippet that stores the chunk ID using a variable as the key (e._posthogChunkIds[n] = "..."), but the regex that searches for it in the bundled output only looks for string literals or numbers as keys — it never matches the variable [n], so the chunk ID is never found. File 2: dist/tooling/posthogMetroSerializer.js — createPostHogMetroSerializer function Even after fixing the regex above, the serializer finds the placeholder string "__POSTHOG_CHUNK_ID__" but

📅 Opened Apr 5, 2026💬 4 comments
Quality: 70/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for PostHog/posthog-js

When evaluating whether to contribute to PostHog/posthog-js, 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 PostHog/posthog-js acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.4% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to PostHog/posthog-js

01

Is PostHog/posthog-js welcoming to first-time open-source contributors?

PostHog/posthog-js has a recorded first-timer success rate of 72.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 65.9 C-Rank™ score represent?

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 65.9 places PostHog/posthog-js in the Welcoming tier.

04

What is the external contributor pull request merge rate for PostHog/posthog-js?

The external pull request merge rate is 77.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in PostHog/posthog-js?

Yes, PostHog/posthog-js currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for PostHog/posthog-js 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.