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

@optima-compliance/export

v0.1.0

Published

Render compliance obligations as iCalendar (RFC 5545) or CSV (RFC 4180).

Readme

@optima-compliance/export

Turn filing obligations into an iCalendar feed (RFC 5545) or a CSV (RFC 4180).

Part of Optima Filings. It takes what @optima-compliance/engine produces and renders it — so a deadline can leave the tool and land in the calendar the person actually looks at.

npm install @optima-compliance/export
import { evaluate } from "@optima-compliance/engine";
import { ALL_RULES } from "@optima-compliance/rules";
import { toICalendar, toCsv } from "@optima-compliance/export";

const obligations = evaluate(entity, ALL_RULES, { asOf: "2026-08-09" });

const ics = toICalendar(obligations, {
  dtstamp: "20260809T120000Z",
  calendarName: "Bright Futures — filings",
  reminderDaysBefore: [30, 7],
});

const csv = toCsv(obligations);

⚠️ Read this before showing a date to anyone

The rules this renders currently ship as status: "draft" — written from general knowledge, not checked against a statute by a person. This package carries that caveat into the calendar event itself, because somebody reading a reminder six months from now on their phone has no other way to know.

Nothing here is legal or tax advice. Every obligation cites its statute; confirm the deadline and the fee with the agency before you file.

It is pure and clock-free

dtstamp is a required parameter with no default, and nothing in this package reads the clock — the same discipline the engine keeps. Two exports of the same obligations produce byte-identical output, which is what makes the result cacheable, diffable, and testable.

The two details that matter

Event UIDs are stable across corrections. A UID is derived from the rule id and the due date, and deliberately not from the title or the fee. A rule corrected upstream therefore updates the event in a subscriber's calendar instead of adding a second one beside it — the failure a user notices immediately and never forgives.

The CSV is safe to open in a spreadsheet. A field beginning =, +, - or @ is a formula to Excel, Numbers and Sheets, and real statute citations begin with -. Those fields are quoted and prefixed with an apostrophe, so a citation stays a citation rather than becoming a broken cell — or a formula-injection vector.

API

| Export | What it does | |---|---| | toICalendar(obligations, options) | An RFC 5545 calendar. options.dtstamp is required; calendarName and reminderDaysBefore are optional | | toCsv(obligations) | An RFC 4180 sheet, one row per obligation | | obligationUid(obligation) | The stable UID for one occurrence, if you are building your own feed | | foldLine(line) | RFC 5545 line folding, exported for callers assembling calendars by hand |

reminderDaysBefore is omitted by default rather than defaulted to one day: a filing deadline you learn about on the day is nearly useless, because most filings take longer than that to prepare. A caller that wants reminders should ask for real notice.

Licence

AGPL-3.0-only. Copyright © 2026 StoneDogCode L.L.C.