yapi

YMFE/yapi

YApi 是一个可本地部署的、打通前后端及QA的、可视化的接口管理平台

Ship status

Gone silent

No push in over 120 days. A quiet repo may also be a finished one.

Last push
Aug 12, 2024
801 days ago
Stars, last 7 weeks
Stars, weekly: 27,721 → 27,703 (Sep 8 – Oct 20, 2026)
−20 stars in the 28 days to 2026-10-20

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
27.7K
Forks
4.8K
Open issues
1.6K
Watchers
520
Primary language
JavaScript
Created
May 30, 2016
Owner
YMFE · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 58 startups in the directory ship primarily in JavaScript.

Topics

#api#api-management#api-manager#api-test

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 76%, self-hostable 95%, hosted offering 47%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: silent — last push 2024-08-12This is the badge for YMFE/yapi, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/YMFE/yapi.svg)](https://ossean.com/YMFE/yapi)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.