officeprops

npm

Is officeprops safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for officeprops v1.1.5. 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)

officeprops 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.

officeprops Capabilities & Permissions

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

Filesystem Access

Reads from the filesystem.

Process Spawning

This package can spawn child processes.

AGENTS.md for officeprops

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

officeprops Documentation & Source Code

For the full officeprops README, API documentation, and source code, visit the official package registry.

Frequently asked questions about officeprops safety

Weekly Downloads

44

Version

1.1.5

License

MIT

Last Scanned

6 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Process

Spawns child processes

Is officeprops Safe? | npm Safety Scan - brin