Item detail
github.com

DeepSeek Recipe

RepoRadar surfaced DeepSeek Recipe — a code repository — into the AI Infrastructure section, where it sits at Silver tier with a 'watch' verdict. Its strongest signal is open-source/build quality, scored 8.4 out of 10.

Score7.0
Popularity100.0
Risknone
TierSilver
Score breakdown
Usefulness7.5
Novelty7.5
Momentum8.0
Maturity7.6
Open-source/build8.4
Evidence7.2
Workflow potential7.4
Setup ease6.4

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

Why it matters

It lowers the cost of reusing DeepSeek's own design choices in other projects: instead of reverse-engineering an architecture from a paper, you import maintained reference code.

Where this stands now

DeepSeek Recipe ranks #72 of 73 tracked AI Infrastructure items by composite score (7.0 against a section median of 8.1). The section currently carries 40 Gold, 32 Silver, 1 Bronze. RepoRadar has retained observations for this record since 2026-09-12 (1 days in the current window). Signal extremes versus the section: momentum at the 79th percentile.

Who should use it

model engineers researchers reusing DeepSeek components

Who should skip it

Pass on DeepSeek Recipe if its scope or audience does not match what your team is building right now.

About this signal

DeepSeek Recipe is tracked by RepoRadar as a code repository in the AI Infrastructure section. First seen 2026-09-12; the source record was last checked on 2026-09-12. The current verdict is 'watch' with a Silver tier and Moderate setup difficulty. DeepSeek Recipe leads on open-source/build quality (8.4) and momentum (8.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. 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 DeepSeek Recipe record combines a 7.0/10 composite score with separate popularity (100.0), risk (none), and setup (Moderate) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

No inherent user-impacting risk: reference code and recipes.

Evidence links
Closest alternatives / related signals
deepseek recipes reference implementations training
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-09-13T05:04:21.529456Z.

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 →

2 dated snapshots retained from 2026-09-12 through 2026-09-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.0 current · +0.0 net
Repository momentum9.0 current · +0.0 net
GitHub stars (observed)319 current · +6 net
GitHub stars319 exact observation
VersionNot reported by source
Last releaseNot reported by source
Maintenanceactive
Current risknone
Current verdictwatch
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-09-137.09.0319nonewatchactive
2026-09-127.09.0313nonewatchactive

Why the record changed

stars changed

Stars changed: 313 → 319.

new entity

Newly added to RepoRadar's decision catalog.