@fawazahmed0/npmpublishtest

npm

Is @fawazahmed0/npmpublishtest safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @fawazahmed0/npmpublishtest v1.0.8. Trust score: 60/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)

@fawazahmed0/npmpublishtest 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.

@fawazahmed0/npmpublishtest Capabilities & Permissions

What @fawazahmed0/npmpublishtest can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads from the filesystem.

package.json (r)

AGENTS.md for @fawazahmed0/npmpublishtest

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

@fawazahmed0/npmpublishtest Documentation & Source Code

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

Frequently asked questions about @fawazahmed0/npmpublishtest safety

Weekly Downloads

28

Version

1.0.8

License

ISC

Last Scanned

4 hours ago

Trust Score

60/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is @fawazahmed0/npmpublishtest Safe? | npm Safety Scan - brin