@the-libs/s3-backend

npm

Is @the-libs/s3-backend safe to use?

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

@the-libs/s3-backend 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.

@the-libs/s3-backend Capabilities & Permissions

What @the-libs/s3-backend 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.

S3_BUCKET_NAME

AGENTS.md for @the-libs/s3-backend

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

@the-libs/s3-backend Documentation & Source Code

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

Frequently asked questions about @the-libs/s3-backend safety

Weekly Downloads

889

Version

1.22.45

Last Scanned

1 day ago

Trust Score

50/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: S3_BUCKET_NAME

Is @the-libs/s3-backend Safe? | npm Safety Scan - brin