Import Provenance Checker
Check an imported or third-party skill's provenance from the evidence the user supplies.
Sample result
How it works
What Import Provenance Checker does
Rates seven dimensions (source identity, commit pin, file integrity through checksums, license, maintainer status, local modifications, security review) as verified, claimed, missing, or conflicting; applies hard gates; assigns a trust tier from quarantine to accepted; drafts conditions, a re-check schedule, and a provenance record to store beside the skill.
Claims made inside the package itself count as claims, never as verification.
Use it when
Someone asks whether an imported skill is traceable, correctly pinned, properly licensed, unmodified, still maintained, or safe to rely on, or wants to decide accept, restrict, or reject.
Use something else for
Scanning a skill's content for malicious behavior, grading how well it is written, or reviewing application dependencies.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
Provenance report, evidence table, trust tier decision and provenance record
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about Import Provenance Checker
Updated Oct 20, 2026.
What does Import Provenance Checker do?
Check an imported or third-party skill's provenance from the evidence the user supplies. Rates seven dimensions (source identity, commit pin, file integrity through checksums, license, maintainer status, local modifications, security review) as verified, claimed, missing, or conflicting; applies hard gates; assigns a trust tier from quarantine to accepted; drafts conditions, a re-check schedule, and a provenance record to store beside the skill. Claims made inside the package itself count as claims, never as verification. Use when someone asks whether an imported skill is traceable, correctly pinned, properly licensed, unmodified, still maintained, or safe to rely on, or wants to decide accept, restrict, or reject. Do not use for scanning a skill's content for malicious behavior (use skill-security-audit), grading how well it is written (use skill-quality-review), or reviewing application dependencies (use dependency-health).
Who is Import Provenance Checker for?
It is designed for catalog maintainers, security and compliance reviewers, platform teams and teams importing third-party skills.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does Import Provenance Checker produce?
Provenance report, evidence table, trust tier decision and provenance record. Results come back with their sources and any open questions for you to check before anything is used.
How much does Import Provenance Checker cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmvgt88rh005k…
- Oct 20, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- rose-digital/relay
- License
- MIT
Connections
Where Import Provenance Checker fits
Have a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.