docs: say the SDKs are open source on every SDK page - #291
Open
tylergoerzen-mxp wants to merge 2 commits into
Open
tylergoerzen-mxp wants to merge 2 commits into
tylergoerzen-mxp wants to merge 2 commits into
Conversation
Add a one-line license + repo statement to each of the 13 SDK pages, add an "Open Source at Mixpanel" page listing every SDK's repository and license, link it from the SDKs overview, and add it to the nav. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Two repos use LICENSE.md and LICENSE.txt, so 'its LICENSE file' was wrong for them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Want your agent to iterate on Greptile's feedback? Try greploops. |
tiffanyqi
approved these changes
Oct 2, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Agents keep calling Mixpanel "closed source." In our AEO tracker's coding runs, 34 of 66 agent explanations for passing on Mixpanel cite PostHog being open source. That's wrong for our SDKs, which are all Apache 2.0 or MIT. But nothing tells agents that: no SDK page or llms.txt mentions open source, and mixpanel.com/open-source 404s.
What changed
docs/tracking-methods/sdks/open-source.mdx, "Open Source at Mixpanel." It has a SDK | Repository | License table for all 13 SDKs, the 5 Session Replay SDKs, and mixpanel-utils. It also says plainly that Mixpanel's platform is a hosted service and isn't open source.docs.jsonand linked it from the SDKs overview (docs/tracking-methods/sdks.mdx).description, so it should show up there after deploy. Nothing to edit here.How facts were verified
gh repo view mixpanel/<repo> --json name,licenseInfo,url,isArchivedon 2026-10-02. All are public and none are archived.gh api repos/mixpanel/<repo>/license, and all five are the Apache License 2.0 text. The table links each license file directly so readers can check.src/recorder) and mixpanel-android (session-replay/module), which matches the 2026-05-11 changelog.html_urlthe GitHub license API returned, so branch names (master vs main) and filenames (LICENSE, LICENSE.md, LICENSE.txt) are exact.Checks
python scripts/check_frontmatter.py,check_code_samples.py,check_links.py,check_redirects.py: all passnpx mint broken-links: no broken links founddocs.jsonparses as valid JSONLinear: TOF-685
🤖 Generated with Claude Code