seafile-js

npm

Is seafile-js safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for seafile-js v0.2.238. 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)

seafile-js 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.

seafile-js Capabilities & Permissions

What seafile-js can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Network Access

This package makes network requests.

Filesystem Access

Reads from the filesystem.

node_modules (r)

AGENTS.md for seafile-js

Good instructions lead to good results. brin adds seafile-js 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 →

seafile-js Documentation & Source Code

For the full seafile-js README, API documentation, and source code, visit the official package registry.

Frequently asked questions about seafile-js safety

Weekly Downloads

377

Version

0.2.238

License

ISC

Last Scanned

2 hours ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Network

Makes network requests

Filesystem

Reads files

Is seafile-js Safe? | npm Safety Scan - brin