zhaopeiym / IoTClient
This is an IoT device communication protocol implementation client, which will include common industrial communication protocols such as mainstream PLC communication reading, ModBus protocol, and Bacnet protocol. This component is open source and free for life, using the most relaxed MIT open source agreement, you can modify and commercial use at will (commercial use please evaluate and test). 这是一个物联网设备通讯协议实现客户端，将会包括主流PLC通信读取、ModBus协议、Bacnet协议等常用工业通讯协议。本组件终身开源免费，采用最宽松的MIT开源协议，您可以随意修改和商业使用（商业使用请做好评估和测试）。
- Stars
- 1,695 stars
- Forks
- 492 forks
- Language
- C#
- License
- MIT
- Created
- Oct 14, 2019
- Last push
- May 12, 2026
- Updated
- Nov 9, 2026
Admitted to the Repository Index on Nov 12, 2026: 1,695 stars on 2026-11-12.
Star History
180 days recorded, May 18, 2026 – Nov 13, 2026 (UTC). Net change +70 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/zhaopeiym/IoTClient) Badge
[](https://awesomerepos.com/zhaopeiym/IoTClient) Timeline
It gained stars on 52 of the 180 days recorded since May 18, 2026.
Its largest 7 days were Jun 7, 2026 to Jun 13, 2026: 8 stars.
In the 30 days to Nov 13, 2026 it got 6 stars, 54% fewer than in the 30 days before.
It had 1,625 stars before May 18, 2026 and has 1,695 stars now: 3,305 fewer than 5,000.
- Created on the Repository Host
- Release 0.4.0: IoTClient
- Latest push
- Largest star day recorded: +3 stars
- +3 stars in one day
- +3 stars in one day
- Entered the Repository Index: 1,695 stars on 2026-11-12
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 13, 2026 – Nov 14, 2026. Forks 0. AwesomeRepos saw a new push on 0 of 1 days.
- Nov 14, 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 zhaopeiym/IoTClient.
Improve the Health Facts of the GitHub repository zhaopeiym/IoTClient. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/zhaopeiym/IoTClient. A change to the repository can improve each of the item below. Each item gives the measured fact or score, and a task. 1. A release in the last 365 days Fact: Newest release 0.4.0 on 2020-09-11, 2255 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. 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 2026-05-12, 186 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)-
No: A release in the last 365 days
Newest release 0.4.0 on 2020-09-11, 2255 days ago. 0 releases in the last 365 days. Source
-
Yes: The newest release tag is a semantic version
The newest release tag is 0.4.0. 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 MIT. 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 14, 2026: 1,695 stars, 492 forks, last push May 12, 2026, not archived. One of 2 Observations since Nov 13, 2026.