@playkit-js/seo

npm

Is @playkit-js/seo safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @playkit-js/seo v1.0.17. Trust score: 85/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)

@playkit-js/seo 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.

@playkit-js/seo Capabilities & Permissions

What @playkit-js/seo 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.

cdnapisec.kaltura.comschema.org
Protocols: https

Process Spawning

This package can spawn child processes.

AGENTS.md for @playkit-js/seo

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

@playkit-js/seo Documentation & Source Code

For the full @playkit-js/seo README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @playkit-js/seo safety

Weekly Downloads

148

Version

1.0.17

License

Apache-2.0

Last Scanned

4 hours ago

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: cdnapisec.kaltura.com, schema.org

Process

Spawns child processes

Is @playkit-js/seo Safe? | npm Safety Scan - brin