langfuse-docs
πͺ’ Open source agent evals & observability: Trace, evaluate, and improve LLM applications with one open platform.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/langfuse/langfuse-docs with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/langfuse/langfuse-docs'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/langfuse--langfuse-docs)HTML
<a href="/listings/langfuse--langfuse-docs"><img src="/api/listings/langfuse--langfuse-docs/badge.svg" alt="findsafeskills safety rating" /></a>Install
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md Β· README Β· 93 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- <img width="2400" height="600" alt="Langfuse" src=".github/readme-banner.png" />
- # Langfuse Docs
- Repo for [langfuse.com](https://langfuse.com). Built with [Fumadocs](https://fumadocs.vercel.app/) and Next.js App Router.
- > ### π§βπ» We're hiring
- >
- > Langfuse is growing fast (we doubled the team in the last 6 months) - since January 2026 we're part of ClickHouse, we're hiring engineers across Europe and in US-East time zones. Marketing and all other roles hire in Europe and all of the United States.
- > We hire engineers who love open source and great developer experiences.
- > **[See open roles β](https://langfuse.com/careers?utm_source=github&utm_medium=readme&utm_campaign=hiring&utm_content=langfuse-docs)**
- ## Local Development
- Pre-requisites: Node.js 22 (22.13+), pnpm v12.8.1
- To use Node 22 (e.g. with [nvm](https://github.com/nvm-sh/nvm)): `nvm install 22` then `nvm use` (or `nvm use 22`). The repo includes an `.nvmrc` so `nvm use` picks 22 automatically.
- 1. Optional: Create env based on [.env.template](./.env.template)
- 2. Run `pnpm i` to install the dependencies.
- 3. Run `pnpm dev` to start the development server on localhost:3333
- ## Formatting
- This repo uses [Prettier](https://prettier.io/) for formatting supported source and content files, including Markdown and MDX.
- - Run `pnpm run format` to format files.
- - Run `pnpm run format:check` to check formatting in CI mode.
- Markdown prose wrapping is preserved and embedded-language formatting is disabled in `.prettierrc.json` so formatting does not change linebreak-sensitive Markdown rendering or fenced code snippet contents.
- ## Python cookbooks
- All Jupyter notebooks are in the `cookbook/` directory. For JS/TS notebooks we use Deno, see Readme in cookbook folder for more details.
- To render them within the documentation site, we convert them to markdown using `jupyter nbconvert`, move them to the right path in the `content/guides/cookbook/` directory where they are picked up by Fumadocs.
- Steps after updating notebooks:
- 1. Ensure you have [uv](https://docs.astral.sh/uv/) installed
- 2. Run `bash scripts/update_cookbook_docs.sh` (uv will automatically handle dependencies)
- 3. Commit the changed markdown files
- **Note**: All `.md` or `.mdx` files that contain "source: β οΈ Jupyter Notebook" on top in `content/guides/cookbook/` are automatically generated from Jupyter notebooks. Do not edit them manually β they will be overwritten. Always edit the Jupyter notebooks and run the conversion script.
- ## Media
- ### Images
- We store all images in the `public/images/` directory. To use them in the markdown files, use the absolute path `/images/your-image.png`.
- ### Videos / Gifs
- We use a bucket on Cloudflare R2 to store all video. It is hosted on https://static.langfuse.com/docs-videos. Ping one of the maintainers to upload a video to the bucket and get the src.
- To embed a video, use the Video component and set a title and fixed aspect ratio. Point src to the mp4 file in the bucket.
- To embed a "gif", actually embed a video and use `gifMode` (`<Video src="" gifMode />`). This will look like a gif, but at a much smaller file size and higher quality.
- ## Stack
- - [Fumadocs](https://fumadocs.vercel.app/) (docs framework)
- - [Next.js](https://nextjs.org/) App Router
- - [shadcn/ui](https://ui.shadcn.com)
- - [Tailwind CSS](https://tailwindcss.com/)
- Interested in stack of Q&A docs chatbot? Checkout the [blog post](https://langfuse.com/blog/qa-chatbot-for-langfuse-docs) for implementation details (all open source)
- ## Search & AI chat
- The docs site uses [Inkeep](https://inkeep.com/) for two separate embeds:
- - **Search** β Inkeep's embedded search widget.
- - **Ask AI chat** β Fumadocs' built-in Inkeep chat integration.
- ## LLM Features
- The docs site includes three interconnected features designed to make documentation accessible to LLMs and AI tools:
- 1. **Markdown URL endpoints** (`.md` suffix): Append `.md` to any URL (e.g., `/docs.md`) to get raw markdown. Built at compile time via `scripts/copy_md_sources.js` which copies all `.mdx`/`.md` files from `content/` to `public/md-src/` as static `.md` files with inlined MDX components.
- 2. **Copy as Markdown button**: UI button on docs pages that fetches the `.md` endpoint and copies to clipboard for pasting into ChatGPT/Claude/Cursor.
- 3. **MCP Server**: Model Context Protocol server at `/api/mcp` with three tools:
- - `searchLangfuseDocs`: RAG search via Inkeep API
- - `getLangfuseDocsPage`: Fetches specific page markdown from `.md` URLs
- - `getLangfuseOverview`: Returns `llms.txt` overview
- Copy and MCP use the same pre-built static Markdown files.
- ## Bundle analysis
- Run `pnpm run analyze` to analyze the bundle size of the production build using `@next/bundle-analyzer`.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If itβs helped, pass it on.