@s3-presigner/server

npm

Is @s3-presigner/server safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @s3-presigner/server v2.1.4. 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)

@s3-presigner/server 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.

@s3-presigner/server Capabilities & Permissions

What @s3-presigner/server 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.

AWS_DEFAULT_REGION

AGENTS.md for @s3-presigner/server

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

@s3-presigner/server Documentation & Source Code

For the full @s3-presigner/server README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @s3-presigner/server safety

Weekly Downloads

42

Version

2.1.4

License

ISC

Last Scanned

3 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Environment

Accesses: AWS_DEFAULT_REGION

Is @s3-presigner/server Safe? | npm Safety Scan - brin