registry / @erannave/react-scheduler / 0.5.3

@erannave/react-scheduler@0.5.3

<div align="center"> <img src="logo.svg" style="height: 60px" alt="@bitnoise/react-scheduler"> <hr /> <p align="center"> ✨ <a href="https://scheduler.bitnoise.pl/">https://scheduler.bitnoise.pl/</a> ✨ <br/> Open sourced, typescript orien

AI Security Review

scanned 4h ago · by lpm-firewall-ai

No confirmed malicious runtime attack surface was found in the shipped scheduler bundle. The only lifecycle behavior is a `prepare` command for Husky, which is a VCS-hook setup risk rather than evidence of payload execution.

Static reason

One or more suspicious static signals were detected.

Trigger

Installing from source or another context that runs npm `prepare` with Husky available

Impact

May configure repository-local Git hooks; no exfiltration, remote payload, or destructive action was found.

Mechanism

Prepare-time Husky invocation

Rationale

No concrete malicious behavior is present in the shipped runtime source. Per policy, the prepare-time VCS-hook setup remains a non-blocking warning despite being package-aligned and apparently benign.

Evidence

package.jsondist/index.jsdist/index.umd.cjsdist/index.cssdist/index.d.tsreadme.md

Network endpoints1

fonts.googleapis.com/css2?family=Inter:wght@400;600;800&display=swap

Decision evidence

public snapshot

AI called this Suspicious at 86.0% confidence as Benign with medium false-positive risk.

@erannave/react-scheduler@0.5.3

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code