Skip to content
Back to search

brekkylab

brekkylab's plugins. Backlot emulates enterprise SaaS APIs over a corpus you supply, so a real client can be built and tested against them.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.

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/brekkylab/backlot 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/brekkylab/backlot'

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
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/brekkylab--backlot/badge.svg)](/listings/brekkylab--backlot)

HTML

<a href="/listings/brekkylab--backlot"><img src="/api/listings/brekkylab--backlot/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

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.

.claude-plugin/marketplace.json · Manifest · 15 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.

  1. {
  2. "name": "brekkylab",
  3. "owner": {
  4. "name": "brekkylab",
  5. "url": "https://github.com/brekkylab"
  6. },
  7. "description": "brekkylab's plugins. Backlot emulates enterprise SaaS APIs over a corpus you supply, so a real client can be built and tested against them.",
  8. "plugins": [
  9. {
  10. "name": "backlot",
  11. "source": "./",
  12. "description": "Emulate an enterprise SaaS knowledge source over a corpus you supply, then wire a real client to it."
  13. }
  14. ]
  15. }
README.md · README · 159 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.

  1. # <picture><source media="(prefers-color-scheme: dark)" srcset="assets/icon/backlot-mark-dark-cropped.svg"><img alt="" src="assets/icon/backlot-mark-light-cropped.svg" height="23"></picture> Backlot
  2. [![GitHub stars](https://img.shields.io/github/stars/brekkylab/backlot?style=social&label=Star)](https://github.com/brekkylab/backlot)
  3. [![python](https://img.shields.io/pypi/pyversions/backlot)](https://pypi.org/project/backlot/)
  4. [![PyPI](https://img.shields.io/pypi/v/backlot)](https://pypi.org/project/backlot/)
  5. [![tests](https://github.com/brekkylab/backlot/actions/workflows/ci.yml/badge.svg)](https://github.com/brekkylab/backlot/actions/workflows/ci.yml)
  6. [![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
  7. [![Discord](https://img.shields.io/badge/Discord-5865F2?logo=discord&logoColor=white)](https://discord.gg/UqmnMFzJtB)
  8. [![X](https://img.shields.io/badge/Tweet-000000?logo=x&logoColor=white)](https://x.com/brekkylab)
  9. **Run enterprise SaaS APIs locally.**
  10. Backlot is a local emulator for Slack, Gmail, Google Drive, Microsoft Teams, GitHub, Jira, Notion, S3 and other enterprise APIs. It reproduces the response shapes, pagination, authentication, errors and per-document access controls an integration has to handle, over a deterministic corpus you control — so you build and test against the official vendor SDKs with **no vendor account**, **no OAuth approval**, **no secrets in CI** and **no network**.
  11. ![Connecting Slack to an app, two ways, side by side. On the left, the real Slack API: create a workspace, register an app, add a bot user, pick OAuth scopes, register a redirect URL, install to the workspace — then wait on an admin to approve it, with still zero API calls made. On the right, Backlot: pip install backlot, backlot import --bundled, backlot serve, and one changed base URL, after which a conversations.history response comes back with the same fields, pagination and per-document ACLs. A day gone, against seconds. Then the same three commands with a different base URL for one source after another, Gmail, Google Drive, Microsoft Teams, GitHub and the rest, each answering a real request. Last, a write on the Slack base URL: chat.postMessage posts a message and conversations.history reads it back; then Backlot's own endpoints at the server root: /_meta/overlay reports what was written, /_meta/overlay/reset puts the corpus back, and the report is empty again.](assets/demo.gif)
  12. ## Try it in 60 seconds
  13. ```bash
  14. pip install backlot
  15. backlot import --bundled # a corpus ships with the package; nothing to fetch or write
  16. backlot serve # every supported API, at http://127.0.0.1:8000
  17. ```
  18. Point an official SDK at it by changing one base URL:
  19. ```python
  20. from slack_sdk import WebClient # pip install slack_sdk
  21. slack = WebClient(token="admin-service-token", base_url="http://127.0.0.1:8000/slack/api/")
  22. print(slack.conversations_list()["channels"])
  23. ```
  24. The same call targets Slack in production and Backlot in development. Backlot supplies the data and the credentials; your code keeps the vendor's request and response contract.
  25. A test can run its own server instead, on a free port, with nothing to start or clean up:
  26. ```python
  27. import backlot
  28. from slack_sdk import WebClient
  29. with backlot.serve() as s: # no arguments: a tiny hello-world corpus
  30. slack = WebClient(token=s.token, base_url=f"{s.base_url}/slack/api/")
  31. channels = slack.conversations_list()["channels"]
  32. ```
  33. ### Let your coding agent run Backlot instantly
  34. This repo is its own plugin marketplace, so the [agent skill](skills/backlot/SKILL.md) installs with no clone and no `pip install` first. Or hand the agent every source as MCP tools: `backlot mcp` starts a server if none is running and serves them all over stdio, with `--user <email>` answering as that person.
  35. ```bash
  36. claude plugin marketplace add brekkylab/backlot && claude plugin install backlot@brekkylab
  37. codex plugin marketplace add brekkylab/backlot && codex plugin add backlot@brekkylab
  38. npx skills add brekkylab/backlot --skill backlot # any agent skills.sh installs into
  39. pip install "backlot[mcp]" && claude mcp add backlot -- backlot mcp # every source as MCP tools
  40. ```
  41. and prompt like this:
  42. > Mock our Slack workspace with three messages in an #incidents channel, get a server running, then show me what `conversations.history` actually returns for that channel.
  43. ## Why not use mocks?
  44. A hand-written mock returns the response your code already expects. Backlot implements the other side of the integration, so it exposes the assumptions a mock would repeat — it is for when the behavior of the API, not just the contents of one response, is what you need to test.
  45. | ❌ Hand-written mocks | ✅ Backlot |
  46. |---|---|
  47. | Test-specific response dictionaries | Vendor-shaped responses served over HTTP |
  48. | Usually cover the happy path | Pagination, validation, auth and vendor-shaped errors |
  49. | Custom test helpers | Official vendor SDKs and ordinary HTTP clients |
  50. | Little or no identity model | Generated users, tokens, groups and document ACLs |
  51. | Fixtures drift between tests | One deterministic corpus, shared locally and in CI |
  52. | Each API mocked differently | Every API served from one process |
  53. ## What it serves
  54. Every source on one local port, each behind the path prefix its own SDK expects, all reading one SQLite corpus.
  55. The corpus defines the facts: messages, files, issues, authors, timestamps, threads, comments, labels, readers. Backlot derives stable ids, users, groups and tokens from them, so every run serves the same records, the same ACL-filtered views and the same pages.
  56. It emulates the documented subset of each API it supports, not every vendor endpoint. The [endpoint-by-endpoint matrix](docs/supported-sources.md) says which, and an implemented endpoint that diverges from the real API is a bug.
  57. <picture><source media="(prefers-color-scheme: dark)" srcset="assets/figures/architecture.png"><img alt="Your code on the left, calling the Slack and GitHub SDKs with only their base URL changed. In the middle, one local server on 127.0.0.1:8000, listing the services it answers as and the path prefix each is served under. On the right, the single SQLite corpus behind all of them." src="assets/figures/architecture-light.png"></picture>
  58. | Service | Base path | Example, on the official SDK |
  59. |---|---|---|
  60. | Slack | `/slack/api` | [`slack.py`](examples/using-official-sdk/slack.py) |
  61. | Gmail | `/gmail/v1` | [`gmail.py`](examples/using-official-sdk/gmail.py) |
  62. | Google Drive (Docs, Sheets, Slides) | `/drive/v3` `/docs/v1` `/sheets/v4` `/slides/v1` | [`gdrive.py`](examples/using-official-sdk/gdrive.py) |
  63. | Microsoft Teams | `/msgraph/v1.0` | [`msteams.py`](examples/using-official-sdk/msteams.py) |
  64. | GitHub | `/github` | [`github.py`](examples/using-official-sdk/github.py) |
  65. | Jira | `/atlassian/rest/api` | [`jira.py`](examples/using-official-sdk/jira.py) |
  66. | Confluence | `/atlassian/wiki/rest/api` | [`confluence.py`](examples/using-official-sdk/confluence.py) |
  67. | Notion | `/notion/v1` | [`notion.py`](examples/using-official-sdk/notion.py) |
  68. | Linear | `/linear/graphql` | [`linear/`](examples/using-official-sdk/linear/) |
  69. | HubSpot | `/hubspot` | [`hubspot.py`](examples/using-official-sdk/hubspot.py) |
  70. | Fireflies | `/fireflies/graphql` | [`fireflies.py`](examples/using-official-sdk/fireflies.py) |
  71. | Amazon S3 | `/s3` | [`s3.py`](examples/using-official-sdk/s3.py) |
  72. The roadmap lives in [the tracking issue](https://github.com/brekkylab/backlot/issues/89) — ask there for the source you need.
  73. ## When you need this
  74. - 🔌 **Building or upgrading an integration**. The cursors, page shapes and error bodies the real API returns, without an account to get them from.
  75. - 🧪 **Testing it, and keeping it tested**. One fixture on your laptop and in CI, with no secrets and nothing to flake. Every user in the corpus gets a token, so you can also assert that one caller's documents never reach another.
  76. - 🤖 **Evaluating a RAG pipeline or an agent**. The same corpus, the same ids and the same answers on every run, so a score that moves means your code moved. Backlot supports write APIs for some vendors, so an agent that acts rather than only reads can be run here and graded on what it actually did — one endpoint reports it, another puts the corpus back for the next run ([docs/write-overlay.md](docs/write-overlay.md)).
  77. - 🐛 **Reproducing a bug in data you can't see**. A document inside someone else's workspace breaks your parser. Write one shaped like it, serve it, and keep the failing test.
  78. ## Bring your own corpus
  79. The bundled corpus covers every supported service, but the main workflow is to serve your own test world: a JSONL file, one source document per line.
  80. ```jsonl
  81. {"source_type":"slack","channel":"incidents","author_email":"bob@acme.com","created":"2026-02-10T18:00:00Z","content":"Anyone seeing 502s from the gateway?","replies":[{"content":"Looking now.","author_email":"ava@acme.com","created":"2026-02-10T18:00:40Z"}]}
  82. ```
  83. ```bash
  84. backlot import my-corpus.jsonl --dry-run # validate against each service's schema, touch nothing
  85. backlot import my-corpus.jsonl && backlot serve
  86. ```
  87. Every imported identity gets deterministic credentials, listed at `GET /_meta/users`; send the same request with another user's token to test what that caller is allowed to see. [Preparing a corpus](docs/corpus.md) covers schemas, rosters, sharded corpora and public datasets, and [Auth and tokens](docs/auth.md) covers each service's authentication style.
  88. ## Examples
  89. | Point this at it | Runnable |
  90. |---|---|
  91. | 📦 Official vendor SDKs, one script per service | [`examples/using-official-sdk/`](examples/using-official-sdk/) |
  92. | 🔗 MCP tools for an agent: `backlot mcp`, or a vendor's own MCP server pointed at Backlot | [`examples/using-mcp-with-agents/`](examples/using-mcp-with-agents/) |
  93. | 🦙 Load it as documents, with the official [LlamaIndex](https://docs.llamaindex.ai/en/stable/module_guides/loading/connector/) readers | [`examples/using-llamaindex-readers/`](examples/using-llamaindex-readers/) |
  94. | 🐍 Read it with `pandas`, `pyarrow` or `dask`, over an [fsspec](https://filesystem-spec.readthedocs.io/) filesystem | [`examples/using-fsspec/`](examples/using-fsspec/) |
  95. | 🗂️ Read it with `ls`, `cat` and `grep`, over [mirage](https://github.com/strukto-ai/mirage)'s virtual filesystem | [`examples/using-mirage/`](examples/using-mirage/) |
  96. | 📥 Your own corpus, from a JSONL file | [`examples/bring-your-own-corpus/`](examples/bring-your-own-corpus/) |
  97. ## Documentation
  98. | | |
  99. |---|---|
  100. | Every source Backlot serves, and every endpoint of each | [docs/supported-sources.md](docs/supported-sources.md) |
  101. | Building a corpus, and public datasets | [docs/corpus.md](docs/corpus.md) |
  102. | Auth schemes and tokens | [docs/auth.md](docs/auth.md) |
  103. | Measuring Backlot against the real APIs | [docs/fidelity.md](docs/fidelity.md) |
  104. | Writes, and where they go | [docs/write-overlay.md](docs/write-overlay.md) |
  105. | Every `BACKLOT_*` setting, and Docker | [docs/configuration.md](docs/configuration.md) |
  106. | Usage telemetry: why it is collected, what is sent, and how to turn it off | [docs/telemetry.md](docs/telemetry.md) |
  107. | Notices and trademarks | [NOTICE.md](NOTICE.md) |
  108. ## Contributing
  109. See [CONTRIBUTING.md](CONTRIBUTING.md). Fidelity to the real APIs is the point, so a divergence is a bug — measure against the real service, and bring a test that fails without your fix.
  110. Backlot exists thanks to all the people who contribute.
  111. <a href="https://github.com/brekkylab/backlot/graphs/contributors"><img alt="Avatars of Backlot's contributors" src="https://raw.githubusercontent.com/brekkylab/backlot/contributors/contributors.svg"></a>
  112. ## License
  113. [Apache-2.0](LICENSE). [NOTICE.md](NOTICE.md) has the MIT License earlier releases were under.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.