Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 174 of 221; 24 results per page.
An SPDX 2.3 JSON SBOM that uses the snippet section to attribute a fictional vendored fragment inside a file to a different licence, with both byte-offset and line-number ranges. Every package, version, hash and licence is fictional: the tree describes nothing real.
An SPDX 3.0 SBOM in JSON-LD (the element-graph model that replaced the 2.x document layout) describing the same fictional tree with software_Package elements and typed Relationship nodes. Every package, version, hash and licence is fictional: the tree describes nothing real.
An SPDX tag-value SBOM whose document name is a fictional container image digest rather than an application version: the naming convention image scanners use, and the SPDX counterpart of the CycloneDX container fixture. Every package, version, hash and licence is fictional: the tree describes nothing real.
An intentionally corrupt SPDX tag-value document, cut off part-way through a tag name so the final line has no colon or value. Kept small on purpose. Every package, version, hash and licence is fictional: the tree describes nothing real.
The input types that behave unlike the rest: a colour picker, a file control, two hidden state fields that carry values without a visible control, and a textarea whose newlines are submitted data rather than layout.
A synthetic absorbance scan from 400 to 630 nm with a Gaussian band at 520 nm, carrying its expanded uncertainty at k=2 in a dedicated column and a per-row quality flag. The unit and the coverage factor live in the column names, which is the convention most instrument exports actually use.
The evented half of the speedscope format: explicit O and C events that must nest like brackets, rather than sampled stacks. Tracing profilers emit this shape, and an unbalanced or out-of-order close is the corruption a loader has to detect.
A speedscope sampled profile: one shared frame table with source locations, then stacks expressed as arrays of frame indices with per-sample weights in nanoseconds. The index indirection is the whole design, and resolving it wrong produces a plausible but wrong flamegraph.
A football-style league table: position, played, won/drawn/lost, goals for/against, goal difference, and points for ten teams, derived from a full round of synthetic match results. Paired with the results JSON.
The full round of match results behind the league table: home/away teams, scores, and dates as a JSON array. A fixture for testing sports-data importers and standings calculators.
RGBA sprite sheet (2×2 cells of 64px) with numbered frames for atlas / CSS-sprite tools.
RGBA sprite sheet (3×2 cells of 64px) with numbered frames for atlas / CSS-sprite tools.
RGBA sprite sheet (4×1 cells of 64px) with numbered frames for atlas / CSS-sprite tools.
A 16-tooth spur-gear profile as a closed DXF polyline with a central hub bore: real parametric CAD geometry (not a primitive). For testing DXF parsers, CAM tools, and CAD conversion.
The same 16-tooth spur-gear profile as STEP AP214 CARTESIAN_POINT entities: the CAD-exchange twin of the DXF, for testing STEP parsing.
Tiny SAMPLE SQL shape (drop-table-comment) for static-analysis demos, not live DDL.
Tiny SAMPLE SQL shape (implicit-cross-join) for static-analysis demos, not live DDL.
Tiny SAMPLE SQL shape (missing-where-update) for static-analysis demos, not live DDL.
Tiny SAMPLE SQL shape (order-by-injection-shape) for static-analysis demos, not live DDL.
Tiny SAMPLE SQL shape (select-star-invalid) for static-analysis demos, not live DDL.
Tiny SAMPLE SQL shape (union-all-dupes) for static-analysis demos, not live DDL.
SQL window function SAMPLE for SQL parsers.
The classic first query in SQL (a single SELECT of a literal) for testing highlighters, SQL parsers, and query editors.
A realistic SQL script with CREATE TABLE constraints and foreign keys, INSERT seed data, a CREATE VIEW, and a grouped aggregate query with a join, for testing SQL parsers, formatters, and highlighters.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.
