@moshebennounorg/signals-sdk-test1
npmIs @moshebennounorg/signals-sdk-test1 safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for @moshebennounorg/signals-sdk-test1 v0.1.0. 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)
@moshebennounorg/signals-sdk-test1 Passed Security Checks
No security concerns detected
0
0
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.
@moshebennounorg/signals-sdk-test1 Capabilities & Permissions
What @moshebennounorg/signals-sdk-test1 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 @moshebennounorg/signals-sdk-test1
Good instructions lead to good results. brin adds @moshebennounorg/signals-sdk-test1 documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
@moshebennounorg/signals-sdk-test1 Documentation & Source Code
For the full @moshebennounorg/signals-sdk-test1 README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @moshebennounorg/signals-sdk-test1 safety
Install (safety-checked)
Weekly Downloads
Version
0.1.0License
SEE LICENSE IN LICENSE_SDK.txtLast Scanned
Trust Score
Capabilities
Connects to: 127.0.0.1, apps.pingone.com, fpjs.dev...
Spawns child processes