jeequan / jeepay
Jeepay是一套适合互联网企业使用的开源支付系统，支持多渠道服务商和普通商户模式。已对接微信支付，支付宝，云闪付官方接口，支持聚合码支付。
Jeepay is an open-source payment system suitable for internet companies, supporting multi-channel service provider and regular merchant modes. It has been integrated with the official interfaces of WeChat Pay, Alipay, and UnionPay QuickPass (云闪付), and supports aggregated code payment. Machine translation by Claude Sonnet 5.5. A wrong translation? Report an error
- Stars
- 6,541 stars
- Forks
- 2,043 forks
- Language
- Java
- License
- LGPL-3.0
- Created
- Aug 12, 2017
- Last push
- Oct 28, 2026
- Updated
- Nov 11, 2026
Why these Tags: an agent read the README and quoted it
- Payment processing from the readme:
一套面向互联网企业的开源支付系统，支持普通商户模式、服务商模式、聚合支付与多应用接入。
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an error with the form at the end of this page.
Admitted to the Repository Index on Nov 10, 2026: 6,536 stars on 2026-11-10.
Star History
188 days recorded, May 8, 2026 – Nov 11, 2026 (UTC). Net change +511 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/jeequan/jeepay) Badge
[](https://awesomerepos.com/jeequan/jeepay) Timeline
It gained stars on 167 of the 188 days recorded since May 8, 2026.
Its largest 7 days were Oct 15, 2026 to Oct 21, 2026: 54 stars.
In the 30 days to Nov 11, 2026 it got 132 stars, 110% more than in the 30 days before.
It had 6,030 stars before May 8, 2026 and has 6,541 stars now: 3,459 fewer than 10,000.
- Created on the Repository Host
- Release V3.2.0
- +10 stars in one day
- Release V3.2.9
- Largest star day recorded: +12 stars
- +10 stars in one day
- Latest push
- Entered the Repository Index: 6,536 stars on 2026-11-10
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 2 Observations, Nov 11, 2026 – Nov 12, 2026. Forks 0. AwesomeRepos saw a new push on 0 of 1 days.
- Nov 12, 2026: no new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos reads the weekly commits, the changelog, and the community files each week for the 5,000 visible repositories with the most stars and for each rising repository. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 1 task for the maintainers of jeequan/jeepay.
Improve the Health Facts of the GitHub repository jeequan/jeepay. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/jeequan/jeepay. A change to the repository can improve each of the item below. Each item gives the measured fact or score, and a task. 1. The newest release tag is a semantic version Fact: The newest release tag is V3.2.9. Rule: The tag of the newest release has the form 1.2.3 or v1.2.3, with an optional pre-release or build part. There is no data when the repository has no release. Task: Make the next release tag a semantic version (1.2.3 or v1.2.3). Do not change or delete a published tag. If a release tool makes the tags, configure it for semantic versions, and write the version scheme in the contributing guide. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
2 of 4 checks (2 without data)-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-10-28, 15 days ago. Source
-
No data: Commits in the last 13 weeks
No data: AwesomeRepos has not read the weekly commits.
-
No data: Commits in 26 or more of the last 52 weeks
No data: AwesomeRepos has not read the weekly commits.
Releases
1 of 3 checks (1 without data)-
Yes: A release in the last 365 days
Newest release V3.2.9 on 2026-05-27, 169 days ago. 2 releases in the last 365 days. Source
-
No: The newest release tag is a semantic version
The newest release tag is V3.2.9. Source
-
No data: A changelog file at the root
No data: AwesomeRepos has not scanned this repository.
Security practice
0 of 1 check (1 without data)-
No data: A security policy
No data: AwesomeRepos has not scanned this repository.
AwesomeRepos has not asked OpenSSF Scorecard about this repository.
Community files
1 of 3 checks (2 without data)-
Yes: A licence
GitHub finds the licence LGPL-3.0. Source
-
No data: A contributing guide
No data: AwesomeRepos has not scanned this repository.
-
No data: A code of conduct
No data: AwesomeRepos has not scanned this repository.
Dependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
The GitHub dependency graph of this repository names 80 direct packages (scanned on Nov 12, 2026). Packages from 13 other repositories in the index are among them.
No scanned repository names a package from this repository.
Uses (in the index) · 13
-
Maven: org.springframework.boot:spring-boot, org.springframework.boot:spring-boot-autoconfigure, org.springframework.boot:spring-boot-maven-plugin, org.springframework.boot:spring-boot-starter-activemq and 7 more
-
Maven: org.springframework:spring-context, org.springframework:spring-webmvc, org.springframework:spring-websocket
- zxing/zxing 34K
Maven: com.google.zxing:core, com.google.zxing:javase
- alibaba/druid 28K
Maven: com.alibaba:druid-spring-boot-3-starter
-
Maven: com.baomidou:mybatis-plus-generator, com.baomidou:mybatis-plus-spring-boot3-starter
-
Maven: com.google.cloud.tools:jib-maven-plugin
-
Maven: org.projectlombok:lombok
- jwtk/jjwt 11K
Maven: io.jsonwebtoken:jjwt
-
Maven: org.springframework.security:spring-security-core
-
GitHub Actions: actions/checkout
Show all 13
-
Maven: io.swagger.core.v3:swagger-models-jakarta
- apache/activemq 2.5K
Maven: org.apache.activemq:activemq-pool
-
Maven: com.mysql:mysql-connector-j
Used by (in the index) · 0
None.
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package (checked on Nov 4, 2026). A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 12, 2026: 6,541 stars, 2,043 forks, last push Oct 28, 2026, not archived. One of 2 Observations since Nov 11, 2026.