CtrlK
BlogDocsLog inGet started
Tessl Logo

meterian/security-audit

Use for dependency security audits and compliance checks. Use when auditing project dependencies for vulnerabilities, answering "is [library] [version] safe?" questions, or remediating vulnerable libraries. Also activates automatically when the user opens or modifies a manifest file (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, requirements.txt, pom.xml, Cargo.toml, go.mod, Gemfile, composer.json, build.gradle, *.csproj, pubspec.yaml, conanfile.txt, conanfile.py, project.clj, deps.edn, Package.swift, pubspec.lock, Package.resolved, Gemfile.lock, poetry.lock, uv.lock, Cargo.lock, composer.lock).

96

1.83x
Quality

90%

Does it follow best practices?

Impact

99%

1.83x

Average score across 8 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Evaluation results

100%

50%

Security Audit: Node.js Order Management API

Node.js full audit with table report

Criteria
Without context
With context

Raw scan data file

30%

100%

Meterian format: safeVersions

0%

100%

nodejs language

0%

100%

Lock file preferred

100%

100%

Markdown table

100%

100%

Correct table headers

41%

100%

Summary line

58%

100%

Remediation offer

100%

100%

Reachability mention

0%

100%

100%

47%

Security Audit: Python Data Processing Service

Python lock file preferred over requirements.txt

Criteria
Without context
With context

python language

0%

100%

Lock file preferred

100%

100%

Pinned versions used

100%

100%

Raw scan data file

26%

100%

Meterian format: safeVersions

0%

100%

Markdown table

40%

100%

Summary line

100%

100%

100%

70%

Security Audit: Go Authentication Microservice

Go module audit with golang language mapping

Criteria
Without context
With context

golang language

0%

100%

go.mod extraction

50%

100%

Raw scan data file

25%

100%

Meterian format: safeVersions

0%

100%

Markdown table

50%

100%

Summary line

100%

100%

100%

33%

Security Audit: Ruby E-Commerce Application

Ruby gems audit with Gemfile.lock preference

Criteria
Without context
With context

ruby language

0%

100%

Gemfile.lock preferred

100%

100%

Pinned versions used

100%

100%

Raw scan data file

33%

100%

Markdown table

70%

100%

Summary line

100%

100%

96%

44%

Security Audit: Java Payment Processing Service

Java Maven audit with pom.xml

Criteria
Without context
With context

java language

0%

100%

pom.xml extraction

90%

80%

Raw scan data file

66%

100%

Meterian format: safeVersions

0%

100%

Markdown table

80%

100%

Summary line

100%

100%

100%

23%

Security Advisory Lookup: squirrel 3.0 (C++)

Ad-hoc library advisory lookup (Mode B)

Criteria
Without context
With context

All 6 advisories found

100%

100%

Severity correct

48%

100%

Descriptions present

100%

100%

Raw advisory data file

100%

100%

Meterian format: versionRange

0%

100%

100%

39%

Security Audit: .NET Payment API

.NET csproj audit with dotnet language mapping

Criteria
Without context
With context

dotnet language

0%

100%

Both csproj files scanned

100%

100%

PackageReference extraction

100%

100%

Raw scan data file

33%

100%

Markdown table

30%

100%

Summary line

100%

100%

100%

57%

Full-Stack Application Security Audit

Multi-language full-stack dependency audit

Criteria
Without context
With context

Finds all manifests

100%

100%

nodejs language

0%

100%

rust language

0%

100%

python language

0%

100%

Raw scan data file

46%

100%

Single scan

33%

100%

Markdown table

69%

100%

Summary line

91%

100%

Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents