Skip to content
Security & Privacy

Safe by design, not by promise

ForgeFeed never asks for or stores your GitHub password or personal access tokens. It authenticates as a GitHub App and acts only within the repository access you explicitly grant.

Security at a glance

No credential handling

GitHub passwords and personal access tokens are never requested or stored. A sign-in token is used once to read who someone is, then dropped. Linking uses GitHub's GitHub App flow.

Owner-only linking

A personal account can only be linked by its owner, signed in as that account. An organization takes someone with admin on every repository the app covers. Linking happens when you press Link on a page that names the server, every step carries a signed token that expires, each button press checks your access on GitHub again, and ForgeFeed records which GitHub user proved each link and when.

Least privilege

The invite asks for eight Discord permissions, each with a stated reason. It doesn't ask for Administrator, Manage Messages, or Manage Server, and it has no Message Content intent, so it does not read messages. Admin replies are private to the admin.

Server isolation

All data is scoped per-server. One server can never see or affect another's repositories, trackers, or configuration.

Hardened surface

Webhook deliveries are cryptographically verified before they are processed, web endpoints are rate limited, and text from GitHub is escaped before it is posted in Discord or shown on a page.

Scoped access, revocable

ForgeFeed acts only within the repository access you grant, and you can revoke it any time from GitHub or with /github unlink.

How linking works

Ownership proven, then linked

Linking uses GitHub's official GitHub App flow plus an owner check, so an install is only ever linked by the account's owner, or by an admin where it's an organization.

  1. On GitHub

    Install the GitHub App

    A manager runs /setup or /github link and presses Install GitHub App, choosing exactly which repositories it may access. If the app is already installed, press Already installed instead of reinstalling.

  2. Signed in to GitHub

    GitHub confirms who you are

    GitHub sends you to a ForgeFeed page that names the server and who started the link. Nothing is linked yet. Only the account's owner can go on, or for an organization, someone with admin on every repository the app covers.

  3. On that page

    Press Link

    Nothing is linked until you press Link on that page. The message in Discord then moves on by itself.

A code for another server looks like this

9f2c41e0 7ab3d58c 6e1f04a7 b92d3c60

Single use · expires in 15 minutes

A link can also be reused in up to 3 of the member's other servers for 7 days, with its own button, so those servers don't each need a fresh Link. It doesn't renew itself, and pressing the plain Link button for that member later ends it. Access can be revoked any time from GitHub or with /github unlink.

Who can link

Only the right person can link

Linking shows a server's members activity from an account's repositories, so being able to see those repositories isn't enough.

Who can link an account

  • A personal account can only be linked by its owner, signed in as that account.
  • An organization takes someone with admin on every repository the app covers. An organization owner always qualifies.
  • Someone with access to only some repositories, or read-only access, is refused, and told who can do it.
  • That proof covers the organization's repositories the app could see at the time. One added to the app later waits until someone with the same access presses Confirm or Keep linked on the page again, and /doctor says which are waiting.
  • If GitHub can't answer while this is checked, the answer is no until it can.

How it stays that way

  • Every step carries a signed token that expires, so a page can't be forged or kept for later.
  • A sign-in that didn't start from a button in Discord does nothing.
  • Pressing a button on the page checks the person's access on GitHub again, so losing it while the page is open stops the buttons working.
  • ForgeFeed records which GitHub user proved each link, and when.
  • A member's /mygithub sign-in only proves who they are. It can't link anything or change what a server can see, and nothing is saved until they confirm on a page that names the Discord member it's for.
  • The page lists every Discord server linked to the account, with an Unlink button for each. Unlinking tells that server's managers and ends any permission to reuse the account.
Roles and pings

Nobody gets more reach than they already had

Anyone who can push to a tracked repository shows up in Discord, so roles and pings are held to what the person setting them up could already do by hand.

Contributor roles

  • Contributor roles are only given below ForgeFeed's own role, and only when added by someone who could give that role by hand.
  • A role that can moderate or manage the server, such as Administrator, Manage Server, Ban Members or Mention @everyone, is refused. If a role gains one of those later, ForgeFeed stops giving it and tells the alerts channel.
  • The invite leaves out Manage Roles. A server that wants contributor roles grants it to ForgeFeed's role itself.

Pings and mentions

  • Setting up a ping of @everyone, or of a role that isn't mentionable, needs Mention Everyone in that channel for the person doing it, the same as sending it by hand, unless they own the server.
  • A comment mentions a member only when one of the repository's owners, members or collaborators wrote it, so a stranger on a public repository can't ping people over and over.
  • A pull request or review by someone outside the repository pings a role once per pull request, so closing and reopening it doesn't ping again.
  • Members who sign in with /mygithub are matched by their GitHub account number, so a renamed account keeps its mentions and whoever takes the old name doesn't get them.
What it can see

Exactly what ForgeFeed touches, and what it never does

ForgeFeed works with

  • The repositories you grant the GitHub App, and the activity it needs to build each post
  • Public repositories added with /repo add, read-only, when no linked account covers them
  • Server, channel, role and user IDs in your configuration
  • GitHub usernames connected to Discord members with /accounts or /mygithub
  • The trackers, boards and settings you set

ForgeFeed never sees

  • Your Discord messages. The only text it sees is a message a member right-clicks with Create GitHub issue or Comment on GitHub, used to fill in the form and not stored
  • Your GitHub password or personal access tokens
  • Private repositories you did not grant it
  • Any other server's repositories, trackers or settings
Under the hood

How delivery stays reliable and verified

Per-installation access

ForgeFeed reads GitHub as a GitHub App. Each installation only reaches the repositories its owner granted, and has its own GitHub quota of 5,000 requests an hour, so one busy server cannot slow down another.

Verified webhooks

Real-time updates arrive over GitHub webhooks, typically within a second. Every delivery is cryptographically verified before it is processed.

Catch-up sweep

A sweep every 15 minutes posts anything a webhook missed, for example while the bot restarted, up to 5 missed updates per tracker per sweep.

Retention

A server's setup is kept for 90 days after the bot is removed, so adding it back restores everything. After that it is deleted.

A tracker that loses access pauses instead of erroring, the server is told, and it resumes on its own when access comes back. When GitHub itself is failing for everyone, nothing is paused or reported as broken.

Bring your repos in, on your terms.

Grant exactly the repositories you choose, revoke anytime, and keep full control from GitHub.

Need organizations or more repositories? Premium, from $4.99 a month for 10 repositories

Join the Discord servers already running ForgeFeed.