@fitness-freak/common

npm

Is @fitness-freak/common safe to use?

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

@fitness-freak/common 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.

@fitness-freak/common Capabilities & Permissions

What @fitness-freak/common 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.

AMQP_URIFIREBASE_ADMINSDK_CONFIGNODE_ENV

AGENTS.md for @fitness-freak/common

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

@fitness-freak/common Documentation & Source Code

For the full @fitness-freak/common README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @fitness-freak/common safety

Weekly Downloads

24

Version

1.4.7

License

ISC

Last Scanned

3 hours ago

Trust Score

50/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: AMQP_URI, FIREBASE_ADMINSDK_CONFIG, NODE_ENV

Is @fitness-freak/common Safe? | npm Safety Scan - brin