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 104 of 221; 24 results per page.
A 256×256 identicon-style avatar generated deterministically from the seed “alan-turing”: a symmetric 5×5 block pattern like the default avatars on many sites. For testing avatar rendering, placeholder generation, and image pipelines.
A 256×256 identicon-style avatar generated deterministically from the seed “grace-hopper”: a symmetric 5×5 block pattern like the default avatars on many sites. For testing avatar rendering, placeholder generation, and image pipelines.
A 256×256 identicon-style avatar generated deterministically from the seed “katherine-johnson”: a symmetric 5×5 block pattern like the default avatars on many sites. For testing avatar rendering, placeholder generation, and image pipelines.
The single-precision counterpart of the float64 boundary array, including the 2^24 integer limit where consecutive whole numbers stop being representable. Widening float32 to float64 and back must preserve every one of these bit patterns.
The float32 boundary values split into sign, 8-bit exponent and 23-bit mantissa alongside their decimal forms. Use it to check a single-precision encoder field by field rather than guessing which end of the number went wrong.
The sixteen structurally distinct float64 values a numeric pipeline has to survive, in binary form: both zeros, both subnormal limits, the smallest normal, epsilon, the largest finite value, both infinities, a quiet NaN and the 2^53 integer boundary. Round-tripping this array is the minimum bar for any float64 codec.
Every value in the float64 boundary array decomposed into its shortest decimal representation, its C99 hexadecimal float form, and its raw sign, exponent and mantissa fields. It turns 'the numbers came back wrong' into a diff you can point at a single bit.
The same boundary values as strict RFC 8259 JSON, where non-finite numbers are null in the numeric field and text in the string field because the standard has no NaN or Infinity literal. It is the fixture for the encoder that emits bare NaN and produces JSON nothing else will parse.
A minimal, well-formed IGES 5.3 file with a single LINE entity and correct Start/Global/Directory/Parameter/Terminate sections. For testing IGES parsers and CAD conversion.
Six synthetic image-caption pairs in JSON Lines, for testing captioning loaders and vision-language eval harnesses.
An image-only PDF containing a rasterised 'scan' of the simple document, with no text layer. Paired with the text version so you can score OCR output against a known ground truth.
School immunization waiver SAMPLE.
The policy half of in-toto: a layout declaring which steps must run, which keys may sign them, and the MATCH/CREATE/DISALLOW artifact rules that bind each step's products to the next step's materials. Signatures, key ids and certificates here are SAMPLE placeholders: the base64 decodes to the words 'SAMPLE SIGNATURE', so verification must fail. Nothing here is cryptographically valid and no key material is real.
An in-toto link file recording one build step: the materials that went in, the products that came out and their sha256 digests, wrapped in the signed/signatures envelope in-toto uses. Signatures, key ids and certificates here are SAMPLE placeholders: the base64 decodes to the words 'SAMPLE SIGNATURE', so verification must fail. Nothing here is cryptographically valid and no key material is real.
The predecessor predicate: SLSA v0.2 uses invocation/materials/buildConfig where v1 uses buildDefinition/runDetails, so this file is the migration test for any verifier that must accept both. Every package, version, hash and licence is fictional: the tree describes nothing real.
An unsigned in-toto Statement carrying a SLSA v1 provenance predicate for a fictional release: build definition, external parameters, resolved dependencies with digests, and run details naming an invented builder. Every package, version, hash and licence is fictional: the tree describes nothing real.
A blameless operational review with impact, timeline, causal analysis, and owned actions. This editable Word edition carries the complete shared family model with styled sections and print-safe tables.
A blameless operational review with impact, timeline, causal analysis, and owned actions. This UTF-8 Markdown twin preserves the same headings, lists, checkboxes, and GFM tables in portable plain text.
A blameless operational review with impact, timeline, causal analysis, and owned actions. This print-ready PDF twin is designed for page-rendering, extraction, and cross-format comparison tests.
Fictional SAMPLE incident runbook Markdown for privacy/security document tooling.
The runbook the alerting rules link to, written as a real one would be: confirm, localise, mitigate, close out, with a symptom table pointing at the trace and profile fixtures in this category. A realistic document for testing runbook linting, link checking and documentation pipelines.
An indexed (palette) instance mask for the fruit still life: background = 0 and each fruit painted with its own instance id. Per-object class and normalised bounding box are listed in the specs.
A classic INI configuration file with sections and key/value pairs, for testing INI parsers.
Clean fruit still-life reference for the inpaint cut suite. Each cut variant and mask in this group points back to this file.
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.
