Item detail
github.com

AIGNE-io/aigne-framework

RepoRadar surfaced AIGNE-io/aigne-framework — a framework — into the Functional TypeScript AI Agent Framework section, where it sits at Silver tier with a 'worth watch' verdict. Its strongest signal is novelty, scored 10.0 out of 10.

Score7.4
Popularity100.0
Riskmedium
TierSilver
Score breakdown
Usefulness7.4
Novelty10.0
Momentum10.0
Maturity7.9
Open-source/build7.4
Evidence7.2
Workflow potential7.8
Setup ease6.5

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for TypeScript-first engineering teams building production AI agents who want a functional, composable framework with a block-based DSL instead of an imperative agent loop, because AIGNE ships @aigne/core plus transport layers for HTTP, CLI, and MCP and provides first-class adapters for OpenAI, Anthropic, Gemini, DeepSeek, and Ollama, which means a developer can model an agent as a graph

Who should use it

Builders Power users

Who should skip it

Hold off on AIGNE-io/aigne-framework for mission-critical workflows without a containment strategy, explicit approvals, and a hands-on security review.

About this signal

AIGNE-io/aigne-framework is tracked by RepoRadar as a framework in the Functional TypeScript AI Agent Framework section. First seen 2026-06-22; the source record was last checked on 2026-06-22. The current verdict is 'worth watch' with a Silver tier and review needed setup difficulty. The standout signals for AIGNE-io/aigne-framework are novelty (10.0) and momentum (10.0), while setup ease (6.5) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The AIGNE-io/aigne-framework record combines a 7.4/10 composite score with separate popularity (100.0), risk (medium), and setup (review needed) signals. See the scoring methodology for the current weights and evidence definitions.

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

Medium risk: use sandboxing, least privilege, and explicit review before connecting sensitive data or accounts.

Evidence links
Closest alternatives / related signals
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

43 dated snapshots retained from 2026-06-22 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score7.4 current · +0.0 net
Repository momentum1.0 current · -9.0 net
GitHub stars (observed)369 current · +1 net
GitHub stars369 exact observation
Versionafs-explorer-v1.2.0-beta
Last release2026-01-20T13:02:32Z
Maintenancestale
Current riskmedium
Current verdictworth watch
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-137.41.0369mediumworth watchstale
2026-08-127.41.0369mediumworth watchstale
2026-08-117.41.0369mediumworth watchstale
2026-08-107.41.0369mediumworth watchstale
2026-08-097.41.0369mediumworth watchstale
2026-08-087.41.0369mediumworth watchstale
2026-08-077.41.0369mediumworth watchstale
2026-08-067.410.0Not recordedmediumworth watchnot recorded
2026-08-057.410.0Not recordedmediumworth watchnot recorded
2026-08-047.41.0369mediumworth watchstale
2026-08-037.41.0369mediumworth watchstale
2026-08-027.41.0369mediumworth watchstale

Why the record changed

maintenance changed

Maintenance changed: slowing → stale.

stars changed

Stars changed: 368 → 369.