Integration idea: machine-readable AI-use observations alongside licence/provenance data

Open
#314 5 comments 0 reactions 0 assignees View on GitHub

@Dev00-1 is already working on this.

Since Nov 6, 2026.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
tooling

Research direction

Start by reading the AboutCode documentation on provenance and licence metadata, then assess how the proposed external AI-use/TDM observations could fit alongside them. The issue names no files, tests, or implementation entry point, so first clarify whether an optional evidence adapter is wanted and what metadata it should record. Done means the project has a decided integration scope; no implementation or acceptance criteria are specified yet.

Written by the indexing model from the issue text.

Description

AboutCode already focuses on provenance, origin and licence information. For AI/data workflows, a complementary upstream signal is the machine-readable AI-use / TDM declaration exposed by a public web source at acquisition time.

AcqPath produces signed timestamped observations for a public resource + intended purpose.

It does not grant licences, determine ownership, prove downstream use, bypass access controls, or interpret UNKNOWN as permission.

Potential integration:

  • external source identified
  • observation state + evidence ID/hash recorded next to licence/provenance metadata
  • downstream policy stays separate
  • later observations can show declaration drift

MCP: https://api.getacqpath.com/mcp

Would this fit as an optional external evidence adapter in the AboutCode ecosystem?

Dominant language
Batchfile
Stars
316
Forks
257
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/aboutcode

All issues in aboutcode-org/aboutcode

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.