trace-codebase-provenance

Trace code provenance in repositories, distinguishing source from derived layers.

1|1|Updated Apr 7, 2026

Search Tags:#code analysis #source code verification #code provenance #deception detection #build dimension analysis

Ready to run

npx skills add https://github.com/quangphu1912/codebase-analyzer --skill trace-codebase-provenance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trace-codebase-provenance
Source: https://github.com/quangphu1912/codebase-analyzer/tree/main/skills/trace-codebase-provenance
Command: npx skills add https://github.com/quangphu1912/codebase-analyzer --skill trace-codebase-provenance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify the true source of code, crucial for accurate analysis, especially when dealing with derived or decompiled code.

Core Features & Use Cases

Provenance Tracking: Distinguishes between source code and derived layers.
Deception Detection: Identifies misleading code structures and hidden contracts.
Build Dimension Analysis: Evaluates the configuration axes examined during code analysis.
Use Case: When analyzing a codebase with unclear origin, this Skill helps determine the source of truth and map the derivation chain.

Quick Start

Run the trace-codebase-provenance Skill to trace the provenance of the current codebase.

Frequently Asked Questions about trace-codebase-provenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I trace the provenance of source code in a repository?▼

To trace source code provenance, you can run this Skill to distinguish original source files from derived layers. It maps the derivation chain to establish the source of truth within your codebase.

What is code provenance tracking and when do I need it?▼

Code provenance tracking identifies the true origin of files, which you need when analyzing decompiled or derived code. It ensures accuracy by verifying whether the code matches its original source structure.

How can I detect deception or hidden contracts in a codebase?▼

You can detect deception by analyzing misleading code structures and hidden contracts. This Skill identifies discrepancies between visible source layers and the actual build dimensions examined.

How do I distinguish source code from derived layers during analysis?▼

Distinguishing source from derived layers requires mapping the build dimensions and derivation chain. This Skill evaluates configuration axes to separate original source from decompiled output.

Does this code verification approach work for decompiled codebases?▼

Yes, it works for decompiled codebases by identifying the true source of truth. It traces the derivation chain to verify code origin and integrity when dealing with unclear provenance.