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

@gcu/plan

v0.1.0

Published

Project scheduling and analysis: CPM, PERT, Monte Carlo, EVM, S-curves, resource leveling, sensitivity. Working calendars with holidays (pt-BR built-in). SVG Gantt and analysis rendering.

Readme

@plan

Project management library for auditable notebooks. CPM scheduling, PERT estimation, Monte Carlo simulation, earned value management, and analysis functions.

usage

const plan = await load("@plan");

modules

| File | Description | |------|-------------| | calendar.js | Working day calculations, holidays, blocked periods | | pert.js | PERT three-point estimation | | graph.js | Topological sort, cycle detection, predecessors/successors | | schedule.js | CPM forward/backward pass, critical path, float | | resource.js | Resource conflict detection, leveling | | scurve.js | S-curve generation (planned/actual/forecast) | | evm.js | Earned value management (BAC, EV, PV, AC, SPI, CPI) | | analysis.js | 16 analysis functions (see below) | | workflow.js | Workflow templates, stage gates, throughput | | montecarlo.js | Monte Carlo simulation with sensitivity tracking | | render.js | SVG renderers (Gantt, S-curve, histogram, tornado, etc.) | | xlsx.js | Excel export | | holidays-br.js | Brazilian holidays (federal, state, municipal) |

analysis functions

  • Schedule: whatIf, delayImpact, nearCritical, slackBudget, scopeDrift, bufferStatus
  • Resource: busFactor, switchingOverhead, meetingCost, constraint
  • Math models: brooksLaw, littlesLaw, multiProjectFragmentation
  • Progress: burndown, health, compress

renderers

gantt, scurvePlot, resourceHistogram, stageGateView, workflowDiagram, monteCarloPlot, deadlineRiskPlot, tornadoPlot, burndownPlot

brazilian holidays

// Federal + state + municipal
const cal = plan.brazilCalendar(2026, 2027, { municipality: "belo horizonte-MG" });
cal.blocked = [{ start: "2026-04-06", end: "2026-04-17", label: "Vacation" }];

// Options: carnival, corpusChristi, optional (pontos facultativos)
plan.brazilMunicipalities(); // list available municipalities

Covers all 27 state capitals + Parauapebas, Canaa dos Carajas, Maraba (PA).

build

node ext/plan/build.js

Concatenates src/*.js into index.js, stripping ES module syntax.

roadmap

rework duration scaling

Current rework transitions in Monte Carlo re-run tasks at full PERT duration. In practice, rework is faster than the original pass (data exists, parameters are tuned, downstream artifacts just need updating). Enhancement:

reworkTransitions: [{
  from: "validation", to: "estimation",
  probability: 0.3,
  durationScale: { estimation: 0.4, validation: 0.5 }
}]

durationScale would multiply the sampled PERT duration on rework iterations, per task. Tasks not listed default to 1.0 (or a configurable defaultReworkScale). This models the reality that re-estimation after a validation failure takes ~40% of original time, not 100%.

not yet implemented (need historical data)

darkTime, gateMetrics, learningCurve, reworkAmplification, referenceClass, overheadRatio, outsourcingAnalysis, fragmentation, utilizationCurve — all require completedInstances / stageHistory data.