Logo

dev-resources.site

for different kinds of informations.

Nosecone: a library for setting security headers in Next.js, SvelteKit, Node.js, Bun, and Deno

Published at
12/10/2024
Categories
nextjs
sveltekit
security
javascript
Author
david-arcjet
Author
12 person written this
david-arcjet
open
Nosecone: a library for setting security headers in Next.js, SvelteKit, Node.js, Bun, and Deno

Nosecone: a library for setting security headers in Next.js, SvelteKit, Node.js, Bun, and Deno

We’re excited to announce Nosecone, an open-source library designed to make setting security headers—like Content Security Policy (CSP) and HTTP Strict Transport Security (HSTS)—straightforward for applications built with Next.js, SvelteKit, and other JavaScript frameworks using Bun, Deno, or Node.js.

While you can always set headers manually, the complexity grows when you need environment-specific configurations, dynamic nonces for inline scripts or styles, or have many variations that need custom configuration.

Whether you’re adapting to the stricter security header requirements of PCI DSS 4.0 which comes into force in 2025 or are simply looking to enhance your app’s security, Nosecone offers:

  • A type-safe API with pragmatic defaults.
  • Middleware adapters for Next.js.
  • Config hooks for SvelteKit.
  • Easy integration with web servers in Bun, Deno, and Node.js.

You can use Nosecone as a standalone library or alongside the Arcjet security as code SDK to further strengthen your app’s defenses against attacks, bots, and spam.

Read our quick start guide and check the source code on GitHub.

Security headers

Nosecone provides a general JS API, a middleware adapter for Next.js, and config hooks for SvelteKit to set sensible defaults. You can test them locally and easily adjust the configuration as code.

Nosecone is open source and supports the following security headers:

  • Content-Security-Policy (CSP)
  • Cross-Origin-Embedder-Policy (COEP)
  • Cross-Origin-Opener-Policy
  • Cross-Origin-Resource-Policy
  • Origin-Agent-Cluster
  • Referrer-Policy
  • Strict-Transport-Security (HSTS)
  • X-Content-Type-Options
  • X-DNS-Prefetch-Control
  • X-Download-Options
  • X-Frame-Options
  • X-Permitted-Cross-Domain-Policies
  • X-XSS-Protection

The defaults look like this:

HTTP/1.1 200 OK
content-security-policy: base-uri 'none'; child-src 'none'; connect-src 'self'; default-src 'self'; font-src 'self'; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; img-src 'self' blob: data:; manifest-src 'self'; media-src 'self'; object-src 'none'; script-src 'self'; style-src 'self'; worker-src 'self'; upgrade-insecure-requests;
cross-origin-embedder-policy: require-corp
cross-origin-opener-policy: same-origin
cross-origin-resource-policy: same-origin
origin-agent-cluster: ?1
referrer-policy: no-referrer
strict-transport-security: max-age=31536000; includeSubDomains
x-content-type-options: nosniff
x-dns-prefetch-control: off
x-download-options: noopen
x-frame-options: SAMEORIGIN
x-permitted-cross-domain-policies: none
x-xss-protection: 0
Content-Type: text/plain
Date: Wed, 27 Nov 2024 21:05:50 GMT
Connection: keep-alive
Keep-Alive: timeout=5
Transfer-Encoding: chunked
Enter fullscreen mode Exit fullscreen mode

Setting Next.js security headers

Nosecone provides a Next.js middleware adapter to set the default headers.

Install with npm i @nosecone/next and then set up this middleware.ts file. See the docs for details.

import { createMiddleware } from "@nosecone/next";

// Remove your middleware matcher so Nosecone runs on every route.

export default createMiddleware();
Enter fullscreen mode Exit fullscreen mode

Setting SvelteKit security headers

Nosecone provides a CSP config and a hook to set the default security headers in SvelteKit.

Install with npm i @nosecone/sveltekit and then set up this svelte.config.js file. See the docs for details.

import adapter from "@sveltejs/adapter-auto";
import { vitePreprocess } from "@sveltejs/vite-plugin-svelte";
import { csp } from "@nosecone/sveltekit"

/** @type {import('@sveltejs/kit').Config} */
const config = {
  preprocess: vitePreprocess(),

  kit: {
    // Apply CSP with Nosecone defaults
    csp: csp(),
    adapter: adapter(),
  },
};

export default config;
Enter fullscreen mode Exit fullscreen mode

With the CSP set on the SvelteKit config, you can then set up the other security headers as a hook in src/hooks.server.ts

import { createHook } from "@nosecone/sveltekit";
import { sequence } from "@sveltejs/kit/hooks";

export const handle = sequence(createHook());
Enter fullscreen mode Exit fullscreen mode

Setting Bun security headers

Nosecone can be connected to your Bun web server to directly set the security response headers.

Install with bun add nosecone and then add this to your server. See the docs for details.

import nosecone from "nosecone";

Bun.serve({
  port: 3000,
  async fetch(req: Request) {
    return new Response("Hello world", {
      headers: nosecone(),
    });
  },
});

Enter fullscreen mode Exit fullscreen mode

Setting Deno security headers

Nosecone works with Deno serve to set the security headers. Install deno add npm:nosecone and then add this to your server. See the docs for details.

import nosecone from "npm:nosecone";

Deno.serve({ port: 3000 }, async (req) => {
  return new Response("Hello world", {
    headers: nosecone(),
  });
});
Enter fullscreen mode Exit fullscreen mode

Setting Node.js security headers

Nosecone can also work with Node.js applications, but if you are using Express.js (by itself or with Remix) then we recommend using Helmet, which informed much of our work on Nosecone.

Install with npm i nosecone and then set this on your Node.js server. See the docs for details.

import nosecone from "nosecone";
import * as http from "node:http";

const server = http.createServer(async function (
  req: http.IncomingMessage,
  res: http.ServerResponse,
) {
  res.setHeaders(nosecone());
  res.writeHead(200, { "Content-Type": "text/plain" });
  res.end("Hello world");
});

server.listen(3000);
Enter fullscreen mode Exit fullscreen mode

Contributing

Nosecone is open source so feel free to submit issues for any improvements or changes. We’re also on Discord if you need help!

sveltekit Article's
30 articles in total
Favicon
Optimize SvelteKit performance with brotli compression
Favicon
SvelteKit VS Astro. laidback side by side
Favicon
Integrating SvelteKit with Storyblok (Using Svelte 5)
Favicon
Make EditorJS work in Svelte(kit) SSR
Favicon
Why Svelte?
Favicon
Nosecone: a library for setting security headers in Next.js, SvelteKit, Node.js, Bun, and Deno
Favicon
Building AI-Powered Apps with SvelteKit: Managing HTTP Streams from Ollama Server
Favicon
NgSysV2-3.4: A Serious Svelte InfoSys: Rules-friendly version
Favicon
NgSysV2-3.3: A Serious Svelte InfoSys: Firebase D/b rules and Login
Favicon
NgSysV2-3.6: A Serious Svelte InfoSys: Deploying to the Google Cloud
Favicon
NgSysV2-3.5: A Serious Svelte InfoSys: Client-Server Version
Favicon
NgSysV2-4.2: SEO (Search Engine Optimisation)
Favicon
NgSysV2-4.3: Automated Svelte Pre-render Builds
Favicon
NgSysV2-4.4: Responsive/Adaptive Design
Favicon
Deploy a Static Sveltekit site to Railway
Favicon
Why You Should Avoid Using `try...catch` in SvelteKit Actions
Favicon
How to integrate shadcn-svelte into the editable.website template
Favicon
PostgreSQL Full Text Search Rank by Position
Favicon
How to Build a Content-Driven Static Site with Markdown, SvelteKit and Fusionable
Favicon
Interview with Prabhu Kiran Konda, Creator of Snail AI!
Favicon
"Helper" Varaibles in Svelte 5
Favicon
Experiences and Caveats of Svelte 5 Migration
Favicon
Running a Function When an #await Block resolves in Svelte(Kit)
Favicon
SanS-UI v0.0.1 Quick Start!
Favicon
Introduction to Svelte: Features and Benefits of the Modern JavaScript Framework
Favicon
Sveltekit + TypeScript + TypeORM + ESM
Favicon
Svelte 5 is out!!!
Favicon
SanS-UI Released v0.0.1
Favicon
How to Integrate Passkeys into SvelteKit
Favicon
AWS Amplify (Gen2) with SvelteKit: authentication on SSR

Featured ones: