acme-dns-01-digitalocean

npm

Is acme-dns-01-digitalocean safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for acme-dns-01-digitalocean v3.0.1. 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)

acme-dns-01-digitalocean 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.

acme-dns-01-digitalocean Capabilities & Permissions

What acme-dns-01-digitalocean can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Network Access

This package makes network requests.

api.digitalocean.comgit.coolaj86.com
Protocols: https

AGENTS.md for acme-dns-01-digitalocean

Good instructions lead to good results. brin adds acme-dns-01-digitalocean 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 →

acme-dns-01-digitalocean Documentation & Source Code

For the full acme-dns-01-digitalocean README, API documentation, and source code, visit the official package registry.

Frequently asked questions about acme-dns-01-digitalocean safety

Weekly Downloads

138

Version

3.0.1

License

MPL-2.0

Last Scanned

14 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: api.digitalocean.com, git.coolaj86.com

Is acme-dns-01-digitalocean Safe? | npm Safety Scan - brin