@forlagshuset/v-search-result

npm

Is @forlagshuset/v-search-result safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @forlagshuset/v-search-result v0.4.7. Trust score: 60/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)

@forlagshuset/v-search-result 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.

@forlagshuset/v-search-result Capabilities & Permissions

What @forlagshuset/v-search-result 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.

AGENTS.md for @forlagshuset/v-search-result

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

@forlagshuset/v-search-result Documentation & Source Code

For the full @forlagshuset/v-search-result README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @forlagshuset/v-search-result safety

Weekly Downloads

37

Version

0.4.7

License

MIT

Last Scanned

1 day ago

Trust Score

60/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is @forlagshuset/v-search-result Safe? | npm Safety Scan - brin