@beisen/pop-layer

npm

Is @beisen/pop-layer safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @beisen/pop-layer v0.1.36. Trust score: 65/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)

@beisen/pop-layer 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.

@beisen/pop-layer Capabilities & Permissions

What @beisen/pop-layer can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Environment Variables

Accesses the following environment variables.

NODE_ENV

AGENTS.md for @beisen/pop-layer

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

@beisen/pop-layer Documentation & Source Code

For the full @beisen/pop-layer README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @beisen/pop-layer safety

Weekly Downloads

264

Version

0.1.36

License

ISC

Last Scanned

1 day ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: NODE_ENV

Is @beisen/pop-layer Safe? | npm Safety Scan - brin