Recordsnpmluxon3.6.1
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| alpine musl | 11 | |
|---|---|---|
| DateTime.localWeekNumber | ||
| DateTime.localWeekYear | ||
| DateTime.startOf | ||
| Info.getMinimumDaysInFirstWeek | ||
| luxon.DateTime | 100%3 | |
| luxon.IANAZone | 67%12 |
Showing the environments with the most evidence.
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.
Environment detail
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
Observations: PROJECT_LOAD 4✓ · PROJECT_TEST 4✓ — Usage: USED 4✓ — Verified: CONTRACT 6✓
|
HIGH | 8 +4 | 6 | 100% | 1 · 3✓ | 2026-08-30 |
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 2✓
|
MEDIUM | 4 +2 | 2 | 100% | 1 · 2✓ | 2026-08-30 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 11✓ 4✕ — Usage: USED 1✓
|
ELEVATED FAILURE | 15 +1 | 0 | 73% | 1 | 2026-08-18 |
Recent failure clusters
-
observed PROJECT_PROCESS Evidence gap ×4 3.6.1 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 luxon.IANAZoneEvidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-17 · Last seen: 2026-08-17Diagnostic re-verification candidate
Symbols
- luxon.DateTime 1 1 of 1 runs passed
- luxon.IANAZone 1 1 of 1 runs passed
- luxon.Info 1
- luxon.Settings 1
- luxon.IANAZone.create 1 2 of 2 runs passed
- Settings.defaultWeekSettings 1 1 of 1 runs passed
- Info.getMinimumDaysInFirstWeek 1 1 of 1 runs passed
- Info.getStartOfWeek 1 1 of 1 runs passed
- DateTime.localWeekNumber 1 1 of 1 runs passed
- DateTime.localWeekYear 1 1 of 1 runs passed
- minimalDays 1
- luxon.DateTime.setZone 1 2 of 2 runs passed
- DateTime.startOf 1 1 of 1 runs passed
Published samples
- luxon 3.6.1 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. HOW MIT-0 · 2026-08-23