EasySpider

NaiboWang/EasySpider

A visual no-code/code-free web crawler/spider易采集:一个可视化浏览器自动化测试/数据采集/网页爬虫软件,可以无代码图形化的设计和执行爬虫任务。别名:ServiceWrapper面向Web应用的智能化服务封装系统。

Ship status

Still shipping

Pushed in the last 30 days.

Last push
7 Nov 2026
5 days ago
Ship score
79/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 44,620 → 44,775 (29 Sep – 10 Nov 2026)
+92 stars in the 28 days to 10 Nov 2026

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
44.8K
Forks
5.4K
Open issues
267
Watchers
234
Primary language
JavaScript
Created
18 Jul 2020
Owner
NaiboWang · User

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

#batch-processing#batch-script#code-free#crawler#data-collection#frontend#gui#html#input-parameters#layman#parameters#robotics#rpa#scraper#spider#visual#visualization#visualprogramming#web#www

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 22 Sep 2026 — os_startup 78%, self-hostable 71%, hosted offering 39%. 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 Sep 2025 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 7 Nov 2026This is the badge for NaiboWang/EasySpider, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/NaiboWang/EasySpider.svg)](https://ossean.com/NaiboWang/EasySpider)

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.