npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@stackoverflow/backstage-plugin-stack-overflow-teams-backend

v1.5.1

Published

Backend counterpart of the Stack Internal Plugin.

Downloads

101

Readme

Stack Internal Backend Plugin

Backend counterpart of the Stack Internal Plugin.

Areas of Responsibility

The Stack Internal Backend plugin is responsible for:

  • Indexing all questions from the private Stack Overflow Internal instance (an enhanced version of the existing community plugins in the Backstage repository).
  • Handling API requests via createStackOverflowApi and createStackOverflowService to the Stack Overflow Internal instance for retrieving:
    • /users
    • /tags
    • /questions
    • Posting new questions via /questions
  • Managing OAuth authentication flow to securely access Stack Overflow Internal private instances via createStackOverflowAuth
  • HTTP-only cookie the Stack Overflow Internal Token is set as a secure http-only cookie to the frontend with 24 hours expiration.

OAuth Authentication Flow

The backend is the only component that directly utilizes the encrypted Stack Overflow Internal access tokens for requests.

Authorization Flow Details

/auth/start

  • Generates PKCE Code Verifier.
  • Hashes Code Verifier to obtain Code Challenge.
  • Generates a state (random string).
  • Stores Code Verifier and State in a secure, HTTP-only cookie accessible only to the server.

/callback

  • Retrieves the stored Code Verifier and State.
  • Validates that the received state matches the one from Stack Overflow Internal's query string parameter.
  • The backend requests an Access Token using the stored Code Verifier.
  • Stores the Stack Overflow Internal Access Token in a secure, HTTP-only cookie.

Installation

This plugin is installed via the @stackoverflow/backstage-plugin-stack-overflow-teams-backend package. To install it to your backend package, run the following command:

yarn --cwd packages/backend add @stackoverflow/backstage-plugin-stack-overflow-teams-backend

Then add the plugin to your backend in packages/backend/src/index.ts:

const backend = createBackend();

// ...

backend.add(import('@stackoverflow/backstage-plugin-stack-overflow-teams-backend'));

Development

This plugin backend can be started in a standalone mode from directly in this package with yarn start. It is a limited setup that is most convenient when developing the plugin backend itself.

If you want to run the entire project, including the frontend, run yarn dev from the root directory.