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

@fullsnacklab/astro-security

v0.2.0

Published

Secure Astro CSP, dynamic response headers, and optional static asset headers.

Readme

@fullsnacklab/astro-security

Secure defaults for Astro's hash-aware page Content Security Policy and dynamic response headers, with optional static-asset _headers output.

The integration owns security plumbing, not application policy. Discovery links, reporting endpoints, third-party origins, report routes, and route-specific exceptions remain explicit application configuration.

Install

bun add @fullsnacklab/astro-security

Use

import { defineConfig } from "astro/config";
import siteSecurity from "@fullsnacklab/astro-security";

export default defineConfig({
  integrations: [siteSecurity()],
});

By default the integration:

  • enables Astro page CSP with SHA-384 hashes;
  • leaves generated script and style hashes to Astro;
  • applies provider-neutral response headers through post middleware;
  • lets application middleware override exceptional route policy while the response unwinds;
  • does not emit reporting or discovery headers with missing application routes.

Customize policy

Pass a complete Astro CSP object when the defaults do not match the application:

siteSecurity({
  csp: {
    algorithm: "SHA-384",
    directives: [
      "default-src 'self'",
      "connect-src 'self' https://analytics.example.com",
      "frame-ancestors 'none'",
    ],
    scriptDirective: {
      resources: ["'self'", "https://challenges.cloudflare.com"],
    },
  },
  headers: {
    "Reporting-Endpoints": 'default="/reports"',
    "X-Frame-Options": null,
  },
});

A null header removes that default. The integration deliberately never copies page CSP into dynamic response middleware because doing so would discard Astro's generated hashes.

Static asset headers

Cloudflare Workers and some other platforms read a _headers build artifact:

siteSecurity({
  staticHeaders: true,
});

This writes the response-header defaults without CSP. To include a serialized static policy explicitly:

siteSecurity({
  staticHeaders: { contentSecurityPolicy: true },
});

Astro's generated page hashes cannot be represented in this file. Enable static CSP only for responses that do not depend on those hashes.

API

  • siteSecurity(options?) — default and named integration factory.
  • createSecurityHeaders(overrides?) — builds a fresh header set.
  • contentSecurityPolicy(config?) — serializes an Astro CSP object for non-rendered responses.
  • staticHeadersArtifact(headers) — formats deterministic _headers content.
  • DEFAULT_CONTENT_SECURITY_POLICY and DEFAULT_SECURITY_HEADERS — documented defaults.

License

MIT