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

@scadable/privacy

v0.2.0

Published

Render your always-current SCADABLE privacy policy in a Next.js app.

Downloads

321

Readme

@scadable/privacy

Render your always-current privacy policy in a Next.js app. You publish the policy once in the SCADABLE app; this component shows whatever version is currently published, so updating your policy never means a redeploy on your side.

Install

npm install @scadable/privacy

Use (App Router)

Drop the component on your privacy page. It is a Server Component, so the policy text is server-rendered (good for SEO) and cached.

import { PrivacyPolicy } from '@scadable/privacy';

export default function PrivacyPage() {
  return (
    <main>
      <PrivacyPolicy token="YOUR_PUBLIC_TOKEN" />
    </main>
  );
}

Get YOUR_PUBLIC_TOKEN from the SCADABLE app after you publish a policy.

Options

| Prop | Type | Default | Notes | | --- | --- | --- | --- | | token | string | required | Your scope's public token. | | className | string | none | Class on the wrapper element. | | showVersion | boolean | false | Show a "Version N, last updated ..." line. | | revalidate | number \| false | 3600 | Next.js ISR seconds. false = always fresh. | | docType | string | "privacy_policy" | Which document to render. | | baseUrl | string | https://api.scadable.com | Override the API base. |

Just the data

If you want to render it yourself:

import { fetchPolicy } from '@scadable/privacy';

const policy = await fetchPolicy('YOUR_PUBLIC_TOKEN');
// { scope_name, domain, version, effective_date, updated_at, html }

policy.html is an HTML content fragment with scoped styles (class scadable-policy), safe to inject inline.

Notes

  • This package only talks to the public SCADABLE API. It stores no secrets.
  • The rendered HTML is your own published policy content from the SCADABLE API.