Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Financial-agent tooling needs explicit approval gates rather than generic chat safeguards. SecondSign is early, but it is useful to track because it turns that need into a concrete authorization layer with receipts and policy checks.
Who should use it
Who should skip it
Avoid running Bestpart-Irene/secondsign-core in production until you have reviewed its permissions, data-access scope, and failure modes in a sandbox.
About this signal
Bestpart-Irene/secondsign-core is tracked by RepoRadar as a code repository in the Financial-agent authorization section. It was first seen on 2026-07-29 and last updated on 2026-07-29. The current verdict is 'worth watch' with a Silver tier and moderate setup difficulty. The standout signals for Bestpart-Irene/secondsign-core are open-source/build quality (8.4) and workflow potential (8.1), while maturity (5.6) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar captured from https://github.com/Bestpart-Irene/secondsign-core. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Bestpart-Irene/secondsign-core a composite score of 7.3 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 12.0 and never affects the composite score or tier. The risk label of 'high' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
financial actions are inherently high-impact and need sandbox testing before real accounts; new project with low adoption signal despite active maintenance; integrations may involve payment, brokerage, or credentialed API access.