C64 VAULT evidence library

OPEN MEDIA / EXACT EVIDENCE

Six files.
Six paper trails.

This is a deliberately small C64 library. Every public item is tied to an author- or project-controlled source, an explicit redistribution basis, immutable bytes, a structural and malware scan, a dated runtime result, and a withdrawal path. The catalog grows only when another candidate clears the same gates.

Why the collection is governed

Large playable catalogs can be useful for discovery, but availability alone does not establish source, permission, integrity, or compatibility. C64 Vault does not copy another site’s catalog and does not infer rights from the fact that a file is downloadable. Each admission record separates program authorship, licensing, artifact identity, firmware, the browser runtime, and observed behavior.

The workbench remains local-first. Hosted artifacts are fetched from this origin and checked in the visitor’s browser before launch. Files chosen from a device are not uploaded and are never represented as part of this verified library. Information pages may carry publisher code, but the isolated emulator root remains ad-free and unoccluded.

6 items

DEMO / PRG

cc65 Plasma

A deterministic C64 plasma graphics demonstration built from the pinned official cc65 sample source and tested in the sanitized browser runtime.

Source
cc65 project
License
Zlib
Evidence
PASS / SHA-256 bound
Read evidence and launch notes →

DEMO / PRG

Fire

A self-generated C64 graphics demonstration from the official cc65 sample tree, producing a continuously animated fire effect.

Source
cc65 project
License
Zlib
Evidence
PASS / SHA-256 bound
Read evidence and launch notes →

GAME / PRG

High Low v1.0

A C64 BASIC number-guessing game preserved from its author-controlled v1.0 release with exact artifact and license evidence.

Source
Keith Ott / ducttape12
License
Apache-2.0
Evidence
PASS / SHA-256 bound
Read evidence and launch notes →

What a PASS means

A PASS is scoped. It means the exact bytes met the recorded gate at the recorded time. A malware scan is not a warranty. A browser launch is not exhaustive functional testing. A license review is not a blanket claim about every upstream component or later version. These limits remain visible so a technical receipt is never used as a proxy for a different kind of proof.

Use each item page for the source revision, retained license, hash, controls, and runtime boundary. Use the public catalog-v2 JSON when machine-readable evidence is needed. Contact the project with a specific item URL and evidence if attribution, licensing, compatibility, or integrity should be re-examined.