@intoss/shared

npm

Is @intoss/shared safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @intoss/shared v0.0.17. Trust score: 50/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)

@intoss/shared 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.

@intoss/shared Capabilities & Permissions

What @intoss/shared 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.intoss.apppreview-api.intoss.appstatic.intoss.app
Protocols: http, https

AGENTS.md for @intoss/shared

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

@intoss/shared Documentation & Source Code

For the full @intoss/shared README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @intoss/shared safety

Weekly Downloads

21

Version

0.0.17

Last Scanned

3 hours ago

Trust Score

50/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: api.intoss.app, preview-api.intoss.app, static.intoss.app

Is @intoss/shared Safe? | npm Safety Scan - brin