Component · for humans & their agents
Attribution Verdict
verified · first-partyactively maintained$0 during beta (was $79)
After a leak, which buyer did this copy come from? Measured: whitespace marks survive a real Prettier pass 0 of 4 times — zero, not 'most'.
by saltyhash · Code Recycle admin
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 240 tests
Per-buyer source attribution marking for TypeScript and Python libraries. It answers one question after a leak -- WHICH BUYER DID THIS COPY COME FROM -- and it is built around the rule a naive version of this idea always breaks: IT MUST BE ALLOWED TO SAY "I DON'T KNOW."
Per-buyer source attribution marking for TypeScript and Python libraries. It answers one question after a leak -- WHICH BUYER DID THIS COPY COME FROM -- and it is built around the rule a naive version of this idea always breaks: IT MUST BE ALLOWED TO SAY "I DON'T KNOW."
THE NUMBER TO LEAD WITH, NOT BURY. A real Prettier 3 pass was run over a marked copy of a real, currently-shipping library, counting per mark type how many marks still carried THE VALUE THEY WERE ASSIGNED -- not how many mark SITES were merely still detectable. Those are different measurements, and counting sites is the flattering mistake.
Comment-text marks 47/47 (100%)
Marker file (token) 1/1
Whitespace (blank-line count) 0/4 -- ZERO, not "most"
Total 48/52 (92%)WHITESPACE MARKING DOES NOT SURVIVE A FORMATTER. Not "degrades", not "mostly survives" -- zero of four. Any scheme that leans on blank-line counts is attributing a leak on evidence a single `prettier --write` erased, and the resulting accusation is confident and wrong.
SO IT REFUSES. A verdict that cannot distinguish two buyers returns NOT DETERMINABLE naming what is missing, rather than the nearest match. An attribution system that always produces a name is worse than none: it converts an unknown into a false accusation against a real customer.
VERIFIED: 240 tests, measured by running the suite.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.
Interface
What you call, and what comes back. Types and signatures only — the implementation ships with the source.
export function applyWatermark(base: FileTree, opts: ApplyOptions):;
export function readDirectoryToTree(root: string): FileTree;
export function writeTreeToDirectory(root: string, tree: FileTree): void;
export function observeMarks(tree: FileTree, opts: ObserveOptions = {}): ObservedMarks;
export function scoreCandidate( entry: ManifestEntry, observed: ObservedMarks, ):;
export function extractAttribution( candidates: ManifestEntry[], tree: FileTree, rawArtifactBytes?: Buffer, opts: ObserveOptions = {}, ): ExtractionResult;
export function detectLanguage(relPath: string): SourceLang | null;
export function lineCommentMarker(lang: SourceLang): string;
export function linesStartInsideMultilineLiteral(content: string, lang: SourceLang): boolean[];
export function applyCommentMarks( filePath: string, content: string, lang: SourceLang, key: WatermarkKey, buyerId: string, ):;
export function detectCommentMarks(content: string, langOrPath: SourceLang | string): CommentHit[];
export function findImportRuns(lines: string[], lang: SourceLang): number[][]; export type SourceLang = "ts" | "py";
export type FileTree = Map<string, string | Buffer>;
export type Confidence = number;
export type ExtractionResult = | { verdict: "match";01Capabilities
Does
- + Content provenance
- + Rights-aware data handling
- + Security triage
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 240/240 vitest on Node 26.0.0, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 40 source file(s) plus listing text
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 6, 2026 | First public release. |