Skip to content
Back to search

flowershow

πŸ’ Publish markdown (and html) websites, docs, wikis and websites in seconds. Integrates with your AI.

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.

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/flowershow/flowershow 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/flowershow/flowershow'

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/flowershow--flowershow/badge.svg)](/listings/flowershow--flowershow)

HTML

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

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

**Prerequisites (for platform development only):** [Node.js 22+](https://nodejs.org/), [pnpm](https://pnpm.io/installation), and [Docker](https://docs.docker.com/get-docker/).

# Clone (include the e2e test-site submodule)
git clone --recurse-submodules https://github.com/flowershow/flowershow.git
cd flowershow

# Install dependencies
pnpm install

# Copy env template (then edit apps/flowershow/.env with your secrets)
cp apps/flowershow/.env.example apps/flowershow/.env

# Start everything: Postgres, MinIO, Inngest, Cloudflare Worker, Next.js app
pnpm dev

Visit `http://cloud.localhost:3000` once it's running.

> If you already cloned without `--recurse-submodules`, run > `git submodule update --init` to fetch the e2e test site.

Commands

pnpm dev --stripe              # Also start Stripe webhook forwarding
pnpm dev --github              # Also start Smee (GitHub webhook proxy)
pnpm dev --search              # Also start Typesense
pnpm dev:all                   # Start everything including all optional services

pnpm dev:local                 # Start dev servers only (no Docker infrastructure)
pnpm dev:local:all             # Start dev servers only + all optional services
pnpm dev:down                  # Stop Docker containers (keep data)
pnpm dev:nuke                  # Stop containers + delete all data volumes

pnpm build                     # Build all packages
pnpm test                      # Run tests across all packages
pnpm lint                      # Lint all packages (ESLint for app, Biome for packages)
pnpm format                    # Check formatting (Biome)
pnpm format:write              # Auto-fix formatting

For web app setup (database, storage, auth, etc.), see [`apps/flowershow/README.md`](apps/flowershow/README.md).

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 Β· 160 lines Β· 1 finding marked

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. [![skills.sh](https://skills.sh/b/flowershow/skills)](https://skills.sh/flowershow/skills)
  2. # Flowershow πŸ’
  3. > ## Publish markdown quickly and easily - for docs, knowledgebases, websites and more
  4. ### Try it out now and sign up at https://flowershow.app/
  5. Want to see it in action? πŸŽ‰ https://flowershow.app itself is built and published with Flowershow πŸ’
  6. - πŸ“ Docs: https://flowershow.app/docs
  7. - πŸ€– for AI: https://flowershow.app/cli
  8. - πŸ’Ž for Obsidian: https://flowershow.app/uses/obsidian
  9. Flowershow is proudly open-source.
  10. Flowershow is a product of [Datopian](https://datopian.com) - dedicated to democratising the power of data & knowledge.
  11. ## Publish
  12. Just login in the website and you can publish in seconds by drag and drop, from Obsidian (plugin), from Github and more.
  13. ### Command line (for AI)
  14. The CLI is a single binary called `fl`.
  15. ```bash
  16. # Install (macOS / Linux)
  17. curl -fsSL https://raw.githubusercontent.com/flowershow/flowershow/main/apps/cli/install.sh | sh
    • Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
    • Line 29 on GitHub
  18. # Log in and publish a folder or file
  19. fl login
  20. fl ./my-notes
  21. ```
  22. Windows: download `fl_windows_amd64.zip` from the [latest release](https://github.com/flowershow/flowershow/releases/latest) and put `fl.exe` on your `PATH`. Full details: [CLI reference](https://flowershow.app/docs/reference/cli).
  23. Using an AI agent (Claude, ChatGPT, Codex, Cursor)? See https://flowershow.app/publish-with-ai.
  24. ---
  25. ---
  26. # For Developers (contributing to Flowershow itself)
  27. **You do not need anything below to use Flowershow.** To install and publish, see [Install and publish](#install-and-publish) above. This section is only for people developing the Flowershow platform from source.
  28. ## Monorepo Structure
  29. This is a [Turborepo](https://turbo.build/) monorepo managed with [pnpm](https://pnpm.io/) workspaces.
  30. ```
  31. apps/
  32. flowershow/ # Next.js web application (flowershow.app)
  33. cli/ # Go CLI (`fl`) β€” publish markdown files from the terminal or AI agents
  34. packages/
  35. api-contract/ # @flowershow/api-contract β€” Zod schemas, TS types, OpenAPI 3.1 spec
  36. cloudflare-worker/ # Markdown processing Cloudflare worker
  37. remark-wiki-link/ # @flowershow/remark-wiki-link β€” remark plugin for wiki-style links
  38. content/
  39. flowershow-app/ # Marketing site content (Obsidian vault, not a workspace package)
  40. ```
  41. ## Development setup
  42. **Prerequisites (for platform development only):** [Node.js 22+](https://nodejs.org/), [pnpm](https://pnpm.io/installation), and [Docker](https://docs.docker.com/get-docker/).
  43. ```bash
  44. # Clone (include the e2e test-site submodule)
  45. git clone --recurse-submodules https://github.com/flowershow/flowershow.git
  46. cd flowershow
  47. # Install dependencies
  48. pnpm install
  49. # Copy env template (then edit apps/flowershow/.env with your secrets)
  50. cp apps/flowershow/.env.example apps/flowershow/.env
  51. # Start everything: Postgres, MinIO, Inngest, Cloudflare Worker, Next.js app
  52. pnpm dev
  53. ```
  54. Visit `http://cloud.localhost:3000` once it's running.
  55. > If you already cloned without `--recurse-submodules`, run
  56. > `git submodule update --init` to fetch the e2e test site.
  57. ### Commands
  58. ```bash
  59. pnpm dev --stripe # Also start Stripe webhook forwarding
  60. pnpm dev --github # Also start Smee (GitHub webhook proxy)
  61. pnpm dev --search # Also start Typesense
  62. pnpm dev:all # Start everything including all optional services
  63. pnpm dev:local # Start dev servers only (no Docker infrastructure)
  64. pnpm dev:local:all # Start dev servers only + all optional services
  65. pnpm dev:down # Stop Docker containers (keep data)
  66. pnpm dev:nuke # Stop containers + delete all data volumes
  67. pnpm build # Build all packages
  68. pnpm test # Run tests across all packages
  69. pnpm lint # Lint all packages (ESLint for app, Biome for packages)
  70. pnpm format # Check formatting (Biome)
  71. pnpm format:write # Auto-fix formatting
  72. ```
  73. For web app setup (database, storage, auth, etc.), see [`apps/flowershow/README.md`](apps/flowershow/README.md).
  74. ## Tooling
  75. | Tool | Scope | Purpose |
  76. | ------------------------------------------------------ | --------------------------- | ---------------------------------------------------------------------- |
  77. | [Biome](https://biomejs.dev/) | Entire repo | Formatting (single quotes, 2-space indent) and linting for `packages/` |
  78. | [ESLint](https://eslint.org/) | `apps/flowershow` | Next.js-specific linting via `eslint-config-next` |
  79. | [Vitest](https://vitest.dev/) | `packages/remark-wiki-link` | Unit tests |
  80. | [Playwright](https://playwright.dev/) | `apps/flowershow` | E2E tests |
  81. | [Turborepo](https://turbo.build/) | Root | Task orchestration and caching |
  82. | [Changesets](https://github.com/changesets/changesets) | `packages/` | Versioning and npm publishing |
  83. | [Husky](https://typicode.github.io/husky/) | Root | Git hooks (pre-commit runs lint-staged) |
  84. A pre-commit hook automatically formats staged files via lint-staged before each commit.
  85. ### Releasing packages
  86. ```bash
  87. pnpm changeset # Create a changeset describing your change
  88. pnpm version-packages # Bump versions based on changesets
  89. pnpm release # Build all packages and publish to npm
  90. ```
  91. ## Documentation
  92. - **Web app**: [`apps/flowershow/README.md`](apps/flowershow/README.md) β€” architecture, local dev setup, environment config, testing, troubleshooting
  93. - **REST API contract**: [`packages/api-contract/README.md`](packages/api-contract/README.md) β€” Zod schemas, TypeScript types, and OpenAPI 3.1 spec for the Flowershow REST API. The contract is the single source of truth for the API surface; the Next.js API routes, CLI, and Obsidian plugin all consume it.
  94. - **Interactive API docs**: With the dev server running, visit `http://cloud.flowershow.local:3000/api/docs` for Swagger UI, or `/api/docs/openapi.json` for the raw spec. In production: [flowershow.app/api/docs](https://flowershow.app/api/docs).
  95. - **CLI**: [`apps/cli/README.md`](apps/cli/README.md) β€” Go CLI for publishing markdown files. Also the interface for AI agent integration β€” see the [Flowershow skill](https://github.com/flowershow/skills).
  96. - **User docs**: [flowershow.app/docs](https://flowershow.app/docs)
  97. ## Community
  98. - Browse [existing issues](https://github.com/flowershow/flowershow/issues) or [submit a new one](https://github.com/flowershow/flowershow/issues/new)
  99. - Visit our [discussions](https://github.com/flowershow/flowershow/discussions) to ask questions, share ideas, or showcase your Flowershow site
  100. ## Contributing
  101. We're working on opening up parts of Flowershow for community contributions. While this isn't ready yet, we're excited to welcome contributors soon.
  102. You can already contribute by adding pull requests for demos or tests of Flowershow markdown features:
  103. - **Demo**: [demo.flowershow.me](https://demo.flowershow.me) β€” [github.com/flowershow/demo](https://github.com/flowershow/demo)
  104. - **Test**: [test.flowershow.me](https://test.flowershow.me/) β€” [github.com/flowershow/test](https://github.com/flowershow/test)
  105. ### Development Workflow
  106. 1. Create feature branch from `staging`
  107. 2. Implement changes
  108. 3. Submit PR to `staging`
  109. 4. After approval, changes are merged to `main`
  110. We use squash merges to `staging` with conventional commit messages.

Ratings and comments

Sign in to rate this skill.

Sign in

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