Recordsnpmcommander15.0.0Command
OS × runtime at a glance
1○ 12026-08-18
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Published samples
- commander 15.0.0: Prove that Commander treats a paired positive and negated boolean flag set as undefined by default. This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWCommandCommand.getOptionValueSourceCommand.optsnode MIT-0 · 2026-08-17
- commander 15.0.0: Prevent silent boolean option default regression in Commander 15 by accounting for paired positive/negative flags remaining undefined instead of defaulting to true like lone negated flags This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWCommandOptionCommand.optionCommand.optsCommand.getOptionValueSourceCommand.parseCommand.addOptionOption.defaultnode MIT-0 · 2026-08-16
- commander 15.0.0: Handle subcommand action argument unpacking, global option propagation via optsWithGlobals, negated boolean flag naming, and custom coerce function radix traps in commander This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWCommandprogram.actionprogram.optsWithGlobalsprogram.optionInvalidArgumentErrornode MIT-0 · 2026-08-16
- commander 15.0.0: Parse command line options with commander without touching process.argv This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWCommandprogram.optionprogram.parsenode 22 MIT-0 · 2026-08-13
- commander 15.0.0: Preserve option value types on optional-value flags by configuring Option.preset() to prevent Commander from coercing valueless flags to boolean true and bypassing argParser This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWOption.presetOption.defaultOption.argParserOptionCommandnode MIT-0 · 2026-08-17
- commander 15.0.0: Configure Option.preset alongside Option.default to prevent bare optional option flags from resolving to boolean true and bypassing custom argParser This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWOption.presetOption.defaultOption.argParserOption.conflictsCommand.getOptionValueSourceCommandOptionnode MIT-0 · 2026-08-16
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux musl · docker
Verified: CONTRACT 7✓
|
MEDIUM | 0 | 7 | 100% | 0 · 2✓ | 2026-08-18 |
| node 22 · JS · npm · linux musl · docker
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-17 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-08-13 |
snapshot · 2026-08-30
Failure clusters
No failure clusters observed.