anomalyco / anomalyco/models.dev

Implement automatic ModelScope model API sync

Open
#1,919 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
6.9k
Forks
1.7k
Avg merge
3h 21m
Merged PRs (30d)
873

Description

Overview

Currently, the ModelScope provider in models.dev only includes a small subset of all the models available on the ModelScope platform. The list of ModelScope models in this repository is rarely updated and does not reflect the full coverage or recent changes from ModelScope.cn.

Problem
  • The ModelScope provider only contains 6 models, which is far less than the actual amount offered on the platform.
  • Models are not kept up to date with additions, removals, or updates from ModelScope.cn.
  • Manual updates require frequent attention and may not be sustainable as the number of models grows.
Proposal

Implement an automated sync mechanism that:

  • Uses the public ModelScope API to fetch available models automatically
  • Implements a periodic sync task (e.g., GitHub Actions workflow or scheduled script) that updates the corresponding TOML files under providers/modelscope/models/
  • Automates additions, removals, and updates to ensure models.dev always reflects the current state of ModelScope.cn
Potential Benefits
  • Ensures model coverage is always up to date
  • Reduces manual maintenance work for contributors
  • Increases the overall usefulness and credibility of models.dev as a reference database
  • Brings parity with other providers that may have similar automation
References
  • ModelScope official platform: https://modelscope.cn
  • ModelScope API documentation: [Add link if available]

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the TOML files under providers/modelscope/models/ and the repository's existing provider data patterns. Review the public ModelScope API and determine how a periodic GitHub Actions workflow or scheduled script should fetch and translate model data. Done means additions, removals, and updates from ModelScope.cn are automatically reflected in those TOML files.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
ai, api, data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.