@pipeliner/core

npm

Is @pipeliner/core safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @pipeliner/core v1.7.4-alpha.0. Trust score: 55/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)

@pipeliner/core 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.

@pipeliner/core Capabilities & Permissions

What @pipeliner/core 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 @pipeliner/core

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

@pipeliner/core Documentation & Source Code

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

Frequently asked questions about @pipeliner/core safety

Weekly Downloads

47

Version

1.7.4-alpha.0

License

GPL-3.0-only

Last Scanned

16 hours ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is @pipeliner/core Safe? | npm Safety Scan - brin