Skip to content

AINativeDev/tessl-audit

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

tessl-audit

npm version License Node.js

Security posture and quality report for the Tessl plugins installed in your project.

Run it in any project that has a tessl.json — no installation required:

npx tessl-audit

Prerequisites

  • Node.js 18 or later
  • A Tessl account, authenticated: tessl auth login (the CLI installs automatically)
  • A tessl.json in your project root

Usage

npx tessl-audit [--json] [path/to/tessl.json]
Flag Description
--json Emit machine-readable JSON instead of the table (useful in CI)
path/to/tessl.json Path to a specific tessl.json (defaults to ./tessl.json)

What you get

Security table

A row per plugin, sorted by risk (most critical first):

  Plugin                               │ Version    │ Type         │ Quality  │  Uplift  │ Security   │ Warnings
  ─────────────────────────────────────────────────────────────────────────────────────────────────────────────
  tessl-labs/intent-integrity-kit      │ 2.9.8      │ skill+rules  │     91%  │   ↑2.1x  │ Passed     │ -
  jbvc/frontend-patterns               │ 0.1.0      │ skill        │     63%  │       -  │ Advisory   │ 1 (W011)
  ...

Columns explained:

Column What it means
Type docs, skill, rules, or skill+rules
Quality Registry quality score — how well-written and complete the plugin is (0–100%)
Uplift How much the plugin improves agent task performance vs baseline (e.g. ↑2.1x)
Security Result of the registry security scan (see below)
Warnings Count and codes of specific warnings from the scan

Security statuses:

Status Meaning
Passed No known issues
Advisory Worth reviewing before use
Risky Do not use without review
Critical Do not use without review
Not run Security scan hasn't been run yet
Unknown Could not fetch data from registry

Summary section

Totals by security status, plus any flagged plugins with their warning codes and links to the full registry security report.

Recommended Actions

After the table, the report gives you concrete next steps:

Quality Review — plugins scoring below 80% quality:

tessl skill review --optimize <publisher/plugin>

Evals Needed — skill plugins with no uplift data yet. Generate scenarios first, then run the eval:

tessl scenario generate --count 5 <publisher/plugin>
tessl eval run <publisher/plugin>

Skill Optimizer — for plugins with low uplift scores or no evals, the skill optimizer can help improve both:

tessl install tessl-labs/skill-optimizer   # install once
# then invoke /tessl__skill-optimizer in Claude Code

JSON output

Use --json to get structured output for CI pipelines or dashboards:

npx tessl-audit --json | jq '.plugins[] | select(.security == "Critical")'

The JSON shape:

{
  "plugins": [
    {
      "plugin": "publisher/plugin",
      "version": "1.0.0",
      "type": "skill",
      "quality": "84%",
      "uplift": "↑1.8x",
      "security": "Passed",
      "warnings": [],
      "reportUrl": "https://tessl.io/registry/publisher/plugin/security"
    }
  ],
  "stats": {
    "quality": { "avg": 82, "min": 63, "max": 97, "below80": ["jbvc/frontend-patterns"] },
    "uplift":  { "avg": 1.9, "min": 1.1, "max": 3.2, "lowImpact": [] },
    "noEvals": ["g14wxz/storage-resumable-upload"]
  }
}

Further reading

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors