@codehz/flecs

npm

Is @codehz/flecs safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @codehz/flecs v0.0.24. 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)

@codehz/flecs Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

1

Install Scripts Detected

postinstall

This package runs scripts during installation. Review these scripts before installing.

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.

@codehz/flecs Capabilities & Permissions

What @codehz/flecs 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 @codehz/flecs

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

@codehz/flecs Documentation & Source Code

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

Frequently asked questions about @codehz/flecs safety

Weekly Downloads

56

Version

0.0.24

Last Scanned

4 hours ago

Trust Score

50/100·Legitimacy signals, not safety

Install Scripts

This package has install scripts that run automatically:

postinstall

Capabilities

Process

Spawns child processes

Is @codehz/flecs Safe? | npm Safety Scan - brin