@threepointone/glam

npm

Is @threepointone/glam safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @threepointone/glam v1.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)

@threepointone/glam 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.

@threepointone/glam Capabilities & Permissions

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

Process Spawning

This package can spawn child processes.

Environment Variables

Accesses the following environment variables.

NODE_ENV

AGENTS.md for @threepointone/glam

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

@threepointone/glam Documentation & Source Code

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

Frequently asked questions about @threepointone/glam safety

Weekly Downloads

9

Version

1.1.0

License

MIT

Last Scanned

23 hours ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Environment

Accesses: NODE_ENV

Is @threepointone/glam Safe? | npm Safety Scan - brin