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

@airmark/quiver

v0.46.0

Published

Airmark Quiver — Air Force, DAF, Army and USACE document Quills for Quillmark.

Readme

@airmark/quiver

A Quillmark source quiver of Air Force, DAF, Army and USACE official-document quills, sourced from tonguetoquill-collection and aligned to the current Quillmark spec.

Quillmark is pre-1.0. Its stability statement says what any release can change and what every release keeps.

Contents

| Quill | Version | Description | |----------------------|---------|----------------------------------------------------------------------------------| | usaf_memo | 0.4.1 | USAF / DAF Official Memorandum (AFH 33-337), with up to four signers | | usaf_memo | 0.4.0 | Previous release, retained so documents pinned to @0.4.0 keep resolving | | usaf_memo | 0.3.0 | Previous release, retained so documents pinned to @0.3 keep resolving | | usaf_memo | 0.2.0 | Previous release, retained so documents pinned to @0.2 keep resolving | | usaf_letter | 0.1.0 | USAF / DAF Personal Letter (AFH 33-337) | | usaf_envelope | 0.0.1 | USAF / DAF envelope (AFH 33-337, chapter 22; draft) | | usaf_paper | 0.1.1 | Point, talking, bullet background, background, and position papers (AFH 33-337) | | usaf_paper | 0.1.0 | Previous release, retained so documents pinned to @0.1.0 keep resolving | | army_memo | 0.1.1 | U.S. Army Memorandum (AR 25-50) | | army_memo | 0.1.0 | Previous release, retained so documents pinned to @0.1.0 keep resolving | | medal_citation | 0.1.0 | Achievement, Meritorious Service, and Commendation Medal citations | | af4141 | 0.1.0 | AF Form 4141 — Individual's Record of Duties and Experience (Ground Environment) | | daf1206 | 0.1.0 | DAF Form 1206 — Nomination for Award | | daf4392 | 0.1.0 | DAF Form 4392 — Pre-Departure Safety Briefing (Page 2) | | afmc_moa | 0.0.1 | DoD Memorandum of Agreement (DoDI 4000.19) | | classic_resume | 0.2.0 | Classic single-page resume | | classic_resume | 0.1.0 | Previous release, retained so documents pinned to @0.1 keep resolving | | cyber_career_plan | 0.1.0 | 17X Cyber Operations Officer career plan: current assignment, vectors and record | | usace_tech_memo | 0.0.1 | USACE technical memorandum (Portland District ENC skeleton; draft) | | usace_report_appendix | 0.0.1 | USACE report appendix (Portland District ENC; draft) | | usace_major_report | 0.0.1 | USACE MMR, MRR, EDR, DDR, Feasibility Study or Phase 1A report (Portland District ENC; draft) |

Install

npm install @airmark/quiver @quillmark/quiver @quillmark/wasm

This package ships the source-quiver assets (Quiver.yaml + quills/) and the official templates, and exposes no JavaScript API. Loading is @quillmark/quiver's, rendering is @quillmark/wasm's.

Usage

Load from the installed directory (Node)

Resolve this package's Quiver.yaml from your own module — your dependencies are reachable from you, not from the loader's install location — and hand its directory to fromDir:

import { createRequire } from 'node:module';
import { dirname } from 'node:path';
import { Engine, init } from '@quillmark/wasm';
import { fromDir } from '@quillmark/quiver/node';

// `init` is the only door to `Document`: there is no static export to reach early.
const { Document } = await init();

const root = dirname(createRequire(import.meta.url).resolve('@airmark/quiver/Quiver.yaml'));
const quiver = await fromDir(root);
const engine = new Engine();

const doc = Document.parse(`~~~
$quill: [email protected]
$kind: main
addressing:
  memo_for: ORG/SYMBOL
  memo_from: |-
    ORG/SYMBOL

    Organization Name

    123 Street Ave

    City ST 12345-6789
  subject: Hello Quillmark
  signature_block: |-
    FIRST M. LAST, Rank, USAF

    Duty Title
~~~

Body of the memo.`);

const quill = await quiver.getQuill(doc.quillRef);
const { artifacts } = await engine.render(quill, doc, { format: 'pdf' });

A quill from getQuill is borrowed: every caller asking for that ref gets the same instance, so it is not yours to free().

Load over HTTP (browser)

A browser cannot read the source layout, so pack it at deploy time and serve the output as static files:

import { build } from '@quillmark/quiver/node'; // build step
await build(root, './public/quivers/airmark');
import { Quiver } from '@quillmark/quiver'; // browser runtime
const quiver = await Quiver.fromBuiltUrl('/quivers/airmark/');

Layout

This package is a source quiver conforming to the canonical layout:

Quiver.yaml
quills/
  <name>/
    <x.y.z>/
      Quill.yaml
      plate.typ
      assets/
      packages/
templates/
  templates.json
  <file>.md

Templates

templates/ holds the official starter documents Tongue to Quill offers in its template library. They sit beside the quiver rather than inside it: the quiver loaders never read them, and a consumer reaches them as files, through @airmark/quiver/templates/templates.json and the Markdown it names. The manifest is { publisher, templates }: publisher is the name the templates are published under, Airmark, which Tongue to Quill's template library shows as their author, and each templates entry is { id, name, description, file, tags }. Every listed template is live.

An entry's id is permanent. Tongue to Quill derives the template's row id and its shareable short code from it, so renaming one retires the old template (its stars and its short code with it) and publishes a new one. Removing an entry retires it the same way.

npm test renders every template against this quiver after quillkit check, and a warning fails it as an error does, so a quill change that breaks a template fails here rather than on the app's build. A typst::pdf_ua warning is the exception: the render exports a tagged PDF that makes no PDF/UA-1 claim.

Working on a quill

How to shape a quill, its fields, groups, seeds, defaults and card kinds, is .claude/skills/quill-design/SKILL.md's: the principles a new or revised Quill.yaml is judged by, and the steps for designing or reviewing one. Claude Code loads it as the quill-design skill.

Two verbs, and they answer different questions.

Both verbs are quillkit's, the quill author's toolchain. It carries @quillmark/quiver and @quillmark/wasm at exact versions, so upgrading quillkit upgrades the format the quiver is packed in and the wasm the gate renders through. This collection pins the same two versions for scripts/check-examples.mjs and scripts/check-templates.mjs, which render through them.

Does it work? quillkit check loads the collection with fromDir, compiles every quill, and renders each one's seed, every field absent but what a card kind's seed: writes and rendering its default: or its blank, and its example, one filled-in page of made-up values: the seed with each field's example: and each kind's body.example committed, one card per kind. npm test then fails a quill that declares no example or whose example warns, and a template that warns. It is the gate CI runs, so a validation failure surfaces here rather than on a consumer's build:

npm install
npm test

The gate renders one answer per quill, so a page with a long list or a wrapping value in it is a design fixture's to exercise (design/).

What is it like to use? npm run dev is quillkit serve: it packs this quiver, drafts included, serves the studio client over it, and repacks on every save — pick a quill, edit its example (or, with Examples off, its seed), watch it paint, read the diagnostics. The client is quillkit's own, so there is nothing to install for it and nothing to keep in step.

Reload to pick up a repack. Editing a quill into an invalid state is not a failure of the loop: it packs, and the client says what is wrong with that quill and where, while the others stay usable.

quillkit check is what CI blocks on, so the gate is authoritative and studio is advisory, though both render through the wasm quillkit carries.

npm run build writes the arrangement a deploy serves into dist/ — the client at the root, a built quiver at quiver/ beneath it — without serving it. It passes --drafts, so the 0.0.x prototypes are packed beside the releases, and npx quillkit preview serves it as a static host will. CI uploads that on every run, so a pull request — a fork's included — is reviewed by downloading the artifact and serving the directory. Studio does not open the templates; npm test is what gates them.

main is deployed to GitHub Pages by .github/workflows/studio.yml, which runs that same command and keeps the deploy here: nothing outside this repository holds pages: write.

vercel.json deploys the same layout to Vercel, where a pull request gets a preview URL instead of an artifact to download. It carries the build, the output directory and the one cache rule a host owes this layout — assets/* immutable, which is studio's own bundle, and everything else already right by default. Importing the repository is the rest of the setup. Both deploys run off main and neither knows about the other.

License

Apache-2.0, the quill packages under quills/ included, except classic_resume's ttq-classic-resume, which is MIT. Two things a quill carries are not the project's to license: the fonts its package bundles, which keep their own upstream terms — see the packages/ directory inside each quill — and the DoD and DoW seals under quills/*/*/assets/, which are US Government insignia and whose use is governed as such.