981011512 / --
停车场系统源码，新能源充电桩系统，停车场小程序，智能停车，Parking system，【功能介绍】：①兼容市面上主流的多家相机，理论上兼容所有硬件，可灵活扩展，②相机识别后数据自动上传到云端并记录，校验相机唯一id和硬件序列号，防止非法数据录入，③用户手机查询停车记录详情可自主缴费(支持微信，支付宝，银行接口支付，支持每个停车场指定不同的商户进行收款)，支付后出场在免费时间内会自动抬杆。④支持app上查询附近停车场(导航，可用车位数，停车场费用，优惠券，评分，评论等)，可预约车位。⑤断电断网支持岗亭人员使用app可接管硬件进行停车记录的录入。 【技术架构】：后端开发语言java，框架oauth2+springboot2+dubble，数据库mysql/mongodb/redis，即时通讯底层框架netty4，安卓和ios均为原生开发，后台管理模板vue专业定制
Parking lot system source code, new energy charging pile system, parking lot mini program, smart parking, Parking system. [Feature introduction]: ① Compatible with many mainstream cameras on the market; in theory compatible with all hardware, and flexibly extensible. ② After a camera recognizes a plate, the data is automatically uploaded to the cloud and recorded; the camera's unique id and hardware serial number are verified to prevent illegal data entry. ③ Users can check parking record details on their phones and pay fees themselves (supports WeChat, Alipay, and bank interface payment; each parking lot can be assigned a different merchant to collect payments). After payment, the barrier gate lifts automatically on exit within the free time. ④ Supports searching for nearby parking lots in the app (navigation, number of available spaces, parking fees, coupons, ratings, reviews, etc.), and parking spaces can be reserved. ⑤ During a power outage or network outage, booth attendants can use the app to take over the hardware and enter parking records. [Technical architecture]: The backend is developed in Java, with the frameworks oauth2 + springboot2 + dubble (Dubbo); databases are mysql/mongodb/redis; the underlying instant messaging framework is netty4; Android and iOS are both developed natively; the admin backend template is a professionally customized vue one. Machine translation by Claude Sonnet 5.5. A wrong translation? Report an error
Read the English README on GitHub (README.en.md, a file of the repository)
- Stars
- 4,718 stars
- Forks
- 2,225 forks
- Language
- Java
- License
- Not reported
- Created
- Jun 18, 2020
- Last push
- Apr 20, 2025
- Updated
- Nov 10, 2026
Admitted to the Repository Index on Nov 10, 2026: 4,719 stars on 2026-11-10.
Star History
184 days recorded, May 12, 2026 – Nov 11, 2026 (UTC). Net change +69 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/981011512/--) Badge
[](https://awesomerepos.com/981011512/--) Timeline
It gained stars on 52 of the 184 days recorded since May 12, 2026.
Its largest 7 days were Jul 2, 2026 to Jul 8, 2026: 9 stars.
In the 30 days to Nov 11, 2026 it got 8 stars, 11% fewer than in the 30 days before.
It had 4,649 stars before May 12, 2026 and has 4,718 stars now: 282 fewer than 5,000.
- Created on the Repository Host
- Latest push
- Largest star day recorded: +4 stars
- +3 stars in one day
- +3 stars in one day
- Entered the Repository Index: 4,719 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 2 tasks for the maintainers of 981011512/--.
Improve the Health Facts of the GitHub repository 981011512/--. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/981011512/--. 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: No GitHub release (read on 2026-11-10). 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. A licence Fact: GitHub finds no licence. Rule: GitHub finds a licence file. When GitHub cannot name the licence, the fact says so. Task: Ask me which licence to use. Do not choose one yourself. Then add the standard licence text as LICENSE at the root, so that GitHub can name the licence. Do not change the terms. Fill in only the fields of the template (for example the year and the copyright holder), and ask me for a value that you cannot verify. 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
1 of 4 checks (2 without data)-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
No: A push in the last 90 days
Last push on 2025-04-20, 571 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
0 of 3 checks (2 without data)-
No: A release in the last 365 days
No GitHub release (read on 2026-11-10). Source
-
No data: The newest release tag is a semantic version
No data: no release.
-
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
0 of 3 checks (2 without data)-
No: A licence
GitHub finds no licence. 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,718 stars, 2,225 forks, last push Apr 20, 2025, not archived. One of 2 Observations since Nov 11, 2026.