@scom/scom-editor

npm

Is @scom/scom-editor safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @scom/scom-editor v0.1.21. 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)

@scom/scom-editor 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.

@scom/scom-editor Capabilities & Permissions

What @scom/scom-editor 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.

Process Spawning

This package can spawn child processes.

AGENTS.md for @scom/scom-editor

Good instructions lead to good results. brin adds @scom/scom-editor 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 →

@scom/scom-editor Documentation & Source Code

For the full @scom/scom-editor README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @scom/scom-editor safety

Weekly Downloads

27

Version

0.1.21

Last Scanned

1 day ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Network

Makes network requests

Process

Spawns child processes

Is @scom/scom-editor Safe? | npm Safety Scan - brin