Standard Subresource Integrity library -- parses, serializes, generates, and verifies integrity metadata according to the SRI spec.
Webpack plugin for enabling Subresource Integrity
The official MongoDB driver for Node.js
A bson parser for node.js and the browser
Fast, fault-tolerant, cross-platform, disk-based, data-agnostic, content-addressable cache.
Microsoft Application Insights Web Snippet
[](https://github.com/mongodb-js/zstd/actions/workflows/test.yml)
JavaScript package downloader
Campfire MCP server — decentralized coordination protocol for AI agents
Require scripts and styles to use Subresource Integrity
A native module that helps assert app integrity on mobile platforms
Collection of toasty utils and configs used by Marshmallow Technology
Official client encryption module for the MongoDB Node.js driver
definitions for some of vlt's core types
Campfire Design System – reusable React components and tokens.
Data Integrity Proof library for use with jsonld-signatures.
Subresource Integrity hashes for the Vite.js manifest.
Fetch package artifacts and metadata from registries
High-performance ESLint/Oxlint plugin that catches dead code, broken imports, and architectural violations. Optimized for monorepos.
React Native package which bridges Andoird Play Integrity API and iOS App Attest
Ergonomic Framework for Human
Jscrambler Code Integrity API client.
Generates SRI hashes for html files
App Attest and App Integrity APIs
Easily let Integrity alert Campfire after each build
Easily let Integrity alert Campfire after each build
Easily let Integrity alert Campfire after each build
Easily let Integrity alert Campfire after each build
A Poundie plugin for integrating WOZZECK wit your Campfire.
Extensible Campfire bot to integrate with other applications/services
Continuous integration should really just be a script that captures the output of running your project update & test commands and presents recent results in a static html page. By keeping test reports in json, per-project CI configuration in 3 probably-one-line scripts, things are kept simple, quick, and super extensible. Want to use git, svn, or hg? No problem. Need to fire off results to Campfire? It's built-in. CI depends on cron.
Continuous integration should really just be a script that captures the output of running your project update & test commands and presents recent results in a static html page. By keeping test reports in json, per-project CI configuration in 3 probably-one-line scripts, things are kept simple, quick, and super extensible. Want to use git, svn, or hg? No problem. Need to fire off results to Twitter or Campfire? It's one line away. CI depends on cron.