whatisgithub

What is lint-plugin-evidence?

samchon/lint-plugin-evidence — explained in plain English

Analysis updated 2026-07-26

3GoAudience · developerComplexity · 3/5Setup · moderate

In one sentence

A lint plugin that makes AI coding agents prove they addressed every project requirement by tagging code with an @evidence comment, causing the build to fail if any obligation is left unaccounted for.

Mindmap

mindmap
  root((repo))
    What it does
      Enforces requirement tracking
      Uses JSDoc evidence tag
      Fails build on gaps
    How it works
      Runs via ttsc wrapper
      Config defines evidence graph
      Errors show as type errors
    Evidence types
      Markdown headings
      TypeScript exports
      Prisma models
      OpenAPI operations
    Use cases
      Auditing AI agent work
      Linking code to docs
      Chaining feature layers
    Tech stack
      TypeScript
      ttsc
      JSDoc
    Audience
      Developers using AI tools

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Audit AI-generated code to ensure every documented requirement has a corresponding evidence tag in the source.

USE CASE 2

Link React components to feature documentation sections so missing implementations fail the build.

USE CASE 3

Chain layered documents together so features cite requirements and tests verify both.

USE CASE 4

Prevent AI agents from silently skipping obligations by making unmet dependencies a compile error.

What is it built with?

TypeScriptttscJSDocGo

How does it compare?

samchon/lint-plugin-evidence12vault/ravelalexremn/finalizer-doctor
Stars333
LanguageGoGoGo
Setup difficultymoderateeasyeasy
Complexity3/52/53/5
Audiencedeveloperdeveloperops devops

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires installing the ttsc compiler wrapper and writing a configuration file that defines your project's evidence graph relationships.

No license information was provided in the explanation.

So what is it?

This project is a lint plugin designed to keep AI coding agents honest when they work on their own. When tools like Claude Code or Codex write code without human supervision, they can skip a requirement and still report the task as complete. Evidence Graph addresses this by making every project requirement demand an explicit acknowledgement from the code, test, or document that claims to satisfy it. The core idea is a JSDoc tag called @evidence. A developer writes a comment above a function that names the exact requirement it fulfills and states why. The compiler does not judge whether that reason is actually true. Instead, it forces the agent to commit to a specific, concrete claim. If an AI fabricates a justification, that claim sits right beside the code for a human reviewer to catch. The result is that an agent can still lie, but it cannot lie by leaving things out. Every configured obligation must be accounted for, or the build fails. The plugin runs through a TypeScript compiler wrapper called ttsc, not the standard tsc tool. You install it alongside @ttsc/lint, then write a configuration file that declares your evidence graph. The graph defines relationships, such as React components in your source folder claiming to implement sections in your documentation folder. If a documentation section exists but no component cites it, the compiler reports an error pointing to the missing citation. These violations appear in the same stream as normal type errors, with no separate checking step required. Graphs can chain together in layers. Feature documents can claim to build on requirement documents, components can claim to implement feature rules, and tests can claim to verify both. The plugin supports Markdown headings, TypeScript exports, Prisma models, and OpenAPI operations as evidence units. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
Help me write a configuration file for lint-plugin-evidence that maps my React components in src/ to feature documents in docs/features/.
Prompt 2
Generate @evidence JSDoc tags for my TypeScript functions that cite the specific requirement IDs from my project's Markdown documentation.
Prompt 3
Show me how to set up ttsc with @ttsc/lint so that evidence graph violations appear alongside normal TypeScript errors in my build output.
Prompt 4
Create a layered evidence graph config where feature docs build on requirement docs, components implement features, and tests verify both.

Frequently asked questions

What is lint-plugin-evidence?

A lint plugin that makes AI coding agents prove they addressed every project requirement by tagging code with an @evidence comment, causing the build to fail if any obligation is left unaccounted for.

What language is lint-plugin-evidence written in?

Mainly Go. The stack also includes TypeScript, ttsc, JSDoc.

What license does lint-plugin-evidence use?

No license information was provided in the explanation.

How hard is lint-plugin-evidence to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is lint-plugin-evidence for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.