Skip to content

Feat/anomaly detection zscore isolation forest#205

Open
Divine-mercyx wants to merge 5 commits into
VertexChainLabs:mainfrom
Divine-mercyx:feat/anomaly-detection-zscore-isolation-forest
Open

Feat/anomaly detection zscore isolation forest#205
Divine-mercyx wants to merge 5 commits into
VertexChainLabs:mainfrom
Divine-mercyx:feat/anomaly-detection-zscore-isolation-forest

Conversation

@Divine-mercyx

Copy link
Copy Markdown
Contributor

closes #190

Pull Request

Please provide a short description of the change and link any related issues.

Description

  • Summary of changes
  • Related issue: # (if applicable)

Checklist

  • Tests added or updated
  • Documentation updated (README, docs, comments)
  • Linting passes
  • Type checking passes (if applicable)
  • Relevant issue linked
  • Changelog updated (if applicable)

Security

If this change includes anything security-sensitive (secrets, auth changes, data exposure), describe mitigations and whether coordinated disclosure is required.

Notes for reviewers

  • Anything specific reviewers should check
  • How to run or reproduce the change locally

Divine-mercyx and others added 5 commits July 16, 2026 09:11
…re and IsolationForest (VertexChainLabs#190)

Move anomaly scoring off the client with simple-statistics rolling z-scores, an isolation-forest worker that emits metrics and alerts, and fixture-backed tests proving injected spikes are flagged.

Co-authored-by: Cursor <cursoragent@cursor.com>
soroban-env-host allows ed25519-dalek >=2.0.0, which now resolves to 3.0.0 and breaks ChaCha20Rng signing in host testutils. Force 2.x on non-wasm targets so Contracts CI compiles again.

Co-authored-by: Cursor <cursoragent@cursor.com>
…file pin

Workspace deps alone still let soroban-env-host compile against ed25519-dalek 3.0. Patch crates.io to the 2.1.1 git tag and generate a pinned lockfile in CI before builds.

Co-authored-by: Cursor <cursoragent@cursor.com>
The git patch pointed at a monorepo tag Cargo cannot resolve. Drop it and rely on generate-lockfile plus cargo update --precise 2.1.1, with workspace dev-deps keeping soroban-env-host off ed25519-dalek 3.0.

Co-authored-by: Cursor <cursoragent@cursor.com>
Cargo resolves both 2.1.1 and 3.0.0, so an unqualified cargo update is ambiguous. Target the 3.0.0 slot explicitly after generate-lockfile.

Co-authored-by: Cursor <cursoragent@cursor.com>

Copy link
Copy Markdown
Contributor

Quick one: PR title is tripping the Conventional Commits lint. Renaming to something like feat(observability): anomaly detection via z-score and isolation forest and pushing should clear it. Pls give it a push!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Anomaly detection: rolling Z-score with IsolationForest server-side

2 participants