Search files, editable visual templates, and live browser targets from one registry-backed directory. Filtered query views stay crawlable for links but are deliberately noindex; the stable taxonomy pages below remain the canonical search surfaces.
Page 14 of 18; 24 results per page.
The baseline proto3 Customer message for field-number and wire-compatibility testing. Reference wire contract: field 1 is string id and field 2 is string name.
The breaking proto3 Customer message for field-number and wire-compatibility testing. Breaking relative to baseline: field number 2 is reused with a different name and wire type.
A realistic Python traceback with a chained exception ('During handling of the above exception...') and a caret error indicator. A fixture for testing traceback parsers and error-reporting tools.
A property-listings dataset — 30 homes with address, type, price, beds/baths, size, year built, coordinates, and status. Synthetic data for testing listing importers, map plots, and price analytics.
The property listings as a JSON array — the format twin of the CSV, for import and mapping tests.
A MovieLens-style ratings log — 240 user/item/rating events with Unix timestamps across 50 users and 40 items. A fixture for testing recommender pipelines, collaborative-filtering loaders, and sparse-matrix builders.
The same three references as an RIS citation file with two-letter tags and ER record terminators — the twin of the BibTeX file, for testing RIS import and BibTeX/RIS conversion.
A 2048-bit RSA private key in unencrypted PKCS#8 PEM — a deliberately PUBLISHED, sample-only key for testing PEM key parsers and PKCS#8 decoders. Never use it for anything real.
A well-formed RSS 2.0 feed with a channel and multiple items — for testing feed readers and parsers.
Synthetic product-analytics events (signup/login/upgrade) for testing event pipelines and warehouse loads. CSV twin.
Synthetic product-analytics events (signup/login/upgrade) for testing event pipelines and warehouse loads. JSON twin.
Sample GraphQL Schema — small deterministic fixture for parsers and the in-browser editor.
The decoded header and payload of the sample JWT as JSON, alongside the public signing secret and algorithm — the ground truth for checking a JWT decoder's output.
A sample JSON Web Token (JWT) signed with HS256 using a published example secret — verifiable but powerless — for testing JWT decoders and validators. Sample only, never for production. Paired with its decoded claims.
Sample Protobuf Schema — small deterministic fixture for parsers and the in-browser editor.
A real SQLite database with two related tables — users and orders joined by a foreign key — for testing database importers and SQL tooling.
A well-formed XML catalogue with nested elements and attributes — for testing XML parsers and XPath queries.
A YAML configuration file with nested mappings, sequences, inline lists, and comments — for testing YAML parsers.
A CSV that uses semicolons as the delimiter (common in European locales) — for testing delimiter detection.
A directed service-dependency graph in GraphML — ten microservices (web, api, auth, db, cache, queue, worker, …) with their call/dependency edges. A fixture for testing directed-graph importers, cycle detection, and topological sorting.
The same 12-person social network in GEXF 1.3 (Gephi's native format) — node attributes and weighted edges. The format twin of the GraphML file, for testing Gephi imports and GraphML↔GEXF conversion.
A small synthetic social network in GraphML — 12 people in two communities with a few bridging ties, carrying node attributes (name, age, community) and weighted edges. Twinned with a GEXF file for testing graph importers and format converters.
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.
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.
