axolot

npm

Is axolot safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for axolot v0.2.5. Trust score: 65/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

axolot Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

No Concerns Detected

No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

axolot Capabilities & Permissions

What axolot can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads and writes to the filesystem.

.env (rw).env (rw)

Process Spawning

This package can spawn child processes.

Environment Variables

Accesses the following environment variables.

NODE_ENVPORT

AGENTS.md for axolot

Good instructions lead to good results. brin adds axolot documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

axolot Documentation & Source Code

For the full axolot README, API documentation, and source code, visit the official package registry.

Frequently asked questions about axolot safety

Weekly Downloads

37

Version

0.2.5

Last Scanned

2 days ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Process

Spawns child processes

Environment

Accesses: NODE_ENV, PORT

Is axolot Safe? | npm Safety Scan - brin