lodik

npm

Is lodik safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for lodik v0.0.35. Trust score: 55/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)

lodik 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.

lodik Capabilities & Permissions

What lodik 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.

developer.chrome.comdeveloper.mozilla.orgdomain.comen.wikipedia.orggithub.comhome.comsome.url.comw3c.github.iowww.pixijs.comwww.w3.org
Protocols: http, https

Process Spawning

This package can spawn child processes.

AGENTS.md for lodik

Good instructions lead to good results. brin adds lodik 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 →

lodik Documentation & Source Code

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

Frequently asked questions about lodik safety

Weekly Downloads

34

Version

0.0.35

License

MIT

Last Scanned

2 days ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: developer.chrome.com, developer.mozilla.org, domain.com...

Process

Spawns child processes

Is lodik Safe? | npm Safety Scan - brin