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

@tenderprompt/tender-app-validator

v0.1.6

Published

Validation library for Tender App source trees.

Readme

Tender App Validator

Validation library for Tender App source trees.

This package powers local CLI checks and can also be reused by Tender server paths before preview, build, Git receive, and publish work. It is a developer feedback tool, not the only security boundary. Server-side validation must still run before accepting or publishing artifact source.

Install

npm install @tenderprompt/tender-app-validator

Usage

import { validateTenderApp } from "@tenderprompt/tender-app-validator";

const result = validateTenderApp({
	files: [
		{
			path: "app.json",
			content: Buffer.from(JSON.stringify({ runtimeClass: "server_backed" })),
		},
		{
			path: "src/server.ts",
			content: Buffer.from("export default {};"),
		},
	],
	mode: "local",
});

if (!result.ok) {
	console.error(result.diagnostics);
}

Validation Modes

  • local: local development feedback.
  • preview: checks before preview work.
  • publish: stricter checks before production publish work.
  • git-receive: checks for source accepted through artifact Git.

What It Checks

  • Tender App manifest shape.
  • edgeCorsPreflight manifest policies for exact-path public-hosting CORS preflight acceleration.
  • Required project files.
  • Managed environment type drift.
  • TypeScript parse errors.
  • suspicious outbound network usage.
  • suspicious secret literals.
  • forbidden repo/cache/build paths such as .git, node_modules, dist, build, .wrangler, .turbo, and .next.

Manifest CORS Preflight Policies

Server-backed apps can opt into public-hosting edge preflight responses for known cross-origin API routes:

{
  "runtimeClass": "server_backed",
  "server": "src/server.ts",
  "edgeCorsPreflight": [
    {
      "path": "/api/free-gift/current",
      "allowedOrigins": ["https://example.com"],
      "allowedMethods": ["POST"],
      "allowedHeaders": ["content-type", "x-example-session"],
      "maxAgeSeconds": 600
    }
  ]
}

Policies are exact-path declarations. They should mirror the CORS behavior in src/server.ts; unknown routes, origins, methods, or headers stay on the normal generated app runner path.

File Input Contract

Pass normalized source files:

type TenderAppFile = {
	path: string;
	content: string | Uint8Array;
};

Paths should be repository-relative POSIX paths. The validator does not read from disk directly.

Security Notes

The validator is intentionally conservative. Some diagnostics are warnings for developer feedback, while errors should block preview or publish in server-side paths. Do not rely on local validation alone; Tender should still validate the artifact source on the server before build or publish.

CLI

For command-line use, install @tenderprompt/cli and run:

tender artifacts doctor --dir ./widget --json