@algolia/ingestion

npm

Is @algolia/ingestion safe to use?

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

@algolia/ingestion 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.

@algolia/ingestion Capabilities & Permissions

What @algolia/ingestion 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.

alg.lidocs.commercetools.comwww.algolia.com
Protocols: https

AGENTS.md for @algolia/ingestion

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

@algolia/ingestion Documentation & Source Code

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

Frequently asked questions about @algolia/ingestion safety

Weekly Downloads

3.1M

Version

1.48.0

License

MIT

Last Scanned

Feb 5, 2026

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: alg.li, docs.commercetools.com, www.algolia.com

Is @algolia/ingestion Safe? | npm Safety Scan - brin