# ruicky/jd_sign_bot

京东签到机器人

Repository: https://github.com/ruicky/jd_sign_bot
Canonical: https://ross.abutalabs.com/products/jd_sign_bot
License Family: other
Archived: true
Last push: 2021-09-29T02:02:19+00:00

## Health v2 (maintenance only)
Score: 10/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 2317, "days_push": 1800, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases, archived, no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4368, forks 7271 (observed 2026-08-28T04:08:46.696053+00:00)

## What it is
A JD.com (Jingdong) sign-in bot that automates daily check-ins on the JD e-commerce platform. The project has been discontinued, with the README replaced by a farewell message.

## Use cases
- automate daily JD.com sign-in rewards
- schedule recurring check-in tasks
- run a self-hosted e-commerce check-in bot

## When to choose
- you need a historical reference for JD sign-in automation approaches

## When to avoid
- you want a maintained, working sign-in bot
- you need support or updates
- JD.com interface changes require active maintenance

## Facets
- artifact type: application
- maturity: abandoned
- function: workflow-automation, scheduling, web-scraping
- domain: e-commerce, developer-tools
- platform: self-hosted
- tags: jd, sign-in-bot, jingdong, discontinued, chinese, automation, nodejs, docker

## Member repositories
- ruicky/jd_sign_bot (main) score 10

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:46.696053+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:21:24.135200+00:00, confidence not recorded.
  - readme: https://github.com/ruicky/jd_sign_bot (fetched 2026-08-28T04:08:46.696053+00:00, sha 6c44d8af7c04)
- Data as of 2026-08-30T08:39:29.467469+00:00.