Recordsnpmlodash-es4.18.1chunk
shared with 2 packages — this evidence cannot say whose API it is
OS × runtime at a glance
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
- lodash-es 4.18.1: Import single lodash functions from lodash-es in an ES module 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. HOWchunkgroupBypicknode 22 MIT-0 · 2026-08-13
- lodash-es 4.18.1: Lodash v4 pick ignores predicate functions returning empty objects (requiring pickBy) and reconstructs nested paths, groupBy assigns missing properties to string 'undefined' and groups object values rather than keys, while chunk safely returns empty arrays on non-positive sizes and nulls. 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. HOWlodash-es.chunklodash-es.groupBylodash-es.picknode 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
Observations: PROJECT_TEST 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-09-07 |
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_TEST 1✓ — Verified: CONTRACT 2✓
|
MEDIUM | 1 | 2 | 100% | 1 · 2✓ | 2026-09-07 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-08-13 |
snapshot · 2026-09-15
Failure clusters
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 4.18.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14Diagnostic re-verification candidate