Recordsnpmcommander15.0.0Command.opts
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
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 3✓
|
MEDIUM | 0 | 3 | 100% | 0 · 2✓ | 2026-08-18 |
snapshot · 2026-08-30
Failure clusters
No failure clusters observed.