brin
brin

@ecomtickets/common

npm

Is @ecomtickets/common safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @ecomtickets/common v1.0.17. Trust score: 40/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)

@ecomtickets/common Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

brin Recommendations

  • →Low trust score. Verify the package source and maintainer reputation before use.

Install with brin add @ecomtickets/common to automatically apply these checks before installation.

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.

@ecomtickets/common Capabilities & Permissions

What @ecomtickets/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.

JWT_KEY

AGENTS.md for @ecomtickets/common

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

@ecomtickets/common Documentation & Source Code

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

View on npm

Frequently asked questions about @ecomtickets/common safety

Weekly Downloads

26

Version

1.0.17

License

ISC

Last Scanned

5 hours ago

Trust Score

40/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: JWT_KEY

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