@openpolitica/matomo-next

npm

Is @openpolitica/matomo-next safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @openpolitica/matomo-next v1.2.1. 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)

@openpolitica/matomo-next 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.

@openpolitica/matomo-next Capabilities & Permissions

What @openpolitica/matomo-next 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 @openpolitica/matomo-next

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

@openpolitica/matomo-next Documentation & Source Code

For the full @openpolitica/matomo-next README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @openpolitica/matomo-next safety

Weekly Downloads

4

Version

1.2.1

License

Apache-2.0

Last Scanned

3 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is @openpolitica/matomo-next Safe? | npm Safety Scan - brin