k-means-constrained

PyPI

Is k-means-constrained safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for k-means-constrained v0.9.0. Trust score: 90/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)

k-means-constrained 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.

k-means-constrained Capabilities & Permissions

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

Environment Variables

Accesses the following environment variables.

SKLEARN_ASSUME_FINITE

Native Modules

Contains native code that runs outside the JavaScript sandbox.

native extensionnumpyscipy

AGENTS.md for k-means-constrained

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

k-means-constrained Documentation & Source Code

For the full k-means-constrained README, API documentation, and source code, visit the official package registry.

Frequently asked questions about k-means-constrained safety

Weekly Downloads

31.5K

Version

0.9.0

Last Scanned

Feb 12, 2026

Trust Score

90/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: SKLEARN_ASSUME_FINITE

Native

Contains native modules