jishenghua / jshERP
管伊佳ERP（原名华夏ERP）基于SpringBoot框架和SaaS模式，立志为中小企业提供开源好用的ERP软件，目前专注进销存+财务功能。主要模块有零售管理、采购管理、销售管理、仓库管理、财务管理、报表查询、系统管理等。支持预付款、收入支出、仓库调拨、组装拆卸、订单等特色功能。拥有库存状况、出入库统计等报表。同时对角色和权限进行了细致全面控制，精确到每个按钮和菜单。
管伊佳ERP (Guanyijia ERP; formerly 华夏ERP, Huaxia ERP) is based on the SpringBoot framework and the SaaS model, and aims to provide small and medium-sized enterprises with open-source, easy-to-use ERP software. It currently focuses on inventory management (purchase, sales and stock) plus finance functions. The main modules are retail management, purchase management, sales management, warehouse management, financial management, report queries, system management, and so on. It supports distinctive features such as prepayments, income and expenses, warehouse transfers, assembly and disassembly, and orders. It provides reports such as stock status and inbound/outbound statistics. It also has detailed and comprehensive control over roles and permissions, down to every button and menu. Machine translation by Claude Sonnet 5.5. A wrong translation? Report an error
- Stars
- 4,699 stars
- Forks
- 1,543 forks
- Language
- Java
- License
- APACHE-2.0
- Created
- Sep 20, 2016
- Last push
- Nov 11, 2026
- Updated
- Nov 11, 2026
Why these Tags: an agent read the README and quoted it
- ERP from the description:
主要模块有零售管理、采购管理、销售管理、仓库管理、财务管理、报表查询、系统管理等。
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: 4,692 stars on 2026-11-10.
Star History
187 days recorded, May 9, 2026 – Nov 11, 2026 (UTC). Net change +477 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/jishenghua/jshERP) Badge
[](https://awesomerepos.com/jishenghua/jshERP) Timeline
It gained stars on 170 of the 187 days recorded since May 9, 2026.
Its largest 7 days were Aug 15, 2026 to Aug 21, 2026: 31 stars.
In the 30 days to Nov 11, 2026 it got 82 stars, 28% more than in the 30 days before.
It had 4,222 stars before May 9, 2026 and has 4,699 stars now: 301 fewer than 5,000.
- Created on the Repository Host
- Release 2.3
- Release 3.1
- Release v3.2
- Release v3.3
- Release v3.5
- +8 stars in one day
- +8 stars in one day
- Largest star day recorded: +9 stars
- Entered the Repository Index: 4,692 stars on 2026-11-10
- Latest push
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 +1. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 12, 2026: 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 2 tasks for the maintainers of jishenghua/jshERP.
Improve the Health Facts of the GitHub repository jishenghua/jshERP. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/jishenghua/jshERP. A change to the repository can improve each of the 2 items below. Each item gives the measured fact or score, and a task. 1. A release in the last 365 days Fact: Newest release v3.5 on 2024-11-11, 731 days ago. 0 releases in the last 365 days. Rule: The newest published GitHub release (a pre-release counts; a draft does not) is 365 days old or less. A repository that publishes only tags, or only to a package registry, has no GitHub release. The release refresh reads the 10 newest releases after each push to the repository, and at least each 30 days. The index refresh reads the date of the last push each day. Task: Prepare a release, but do not publish it. Find the changes since the newest release, propose the next semantic version and the release notes, and ask me to publish the GitHub release. If nothing changed since the newest release, skip this item. If the project publishes only to a package registry, add a CI step that also makes a GitHub release for each version tag. 2. The newest release tag is a semantic version Fact: The newest release tag is v3.5. 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-11-11, 1 day 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
0 of 3 checks (1 without data)-
No: A release in the last 365 days
Newest release v3.5 on 2024-11-11, 731 days ago. 0 releases in the last 365 days. Source
-
No: The newest release tag is a semantic version
The newest release tag is v3.5. 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 APACHE-2.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.
Observations
Latest Observation, Nov 12, 2026: 4,699 stars, 1,543 forks, last push Nov 11, 2026, not archived. One of 2 Observations since Nov 11, 2026.