LingX-AI / LinkSense
The open-source alternative to WorkBuddy / ChatGPT Enterprise.
- Stars
- 283 stars
- Forks
- 60 forks
- Language
- TypeScript
- License
- OTHER
- Created
- Aug 31, 2026
- Last push
- Nov 13, 2026
- Updated
- Nov 13, 2026
Why these Tags: an agent read the README and quoted it
- Personal AI assistant from the readme:
LinkSense gives organizations one governed place to run agent tasks, share reusable Knowledge, Skills, Plugins, and Applications
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 12, 2026: +121 stars in 7 days.
Star History
74 days recorded, Sep 1, 2026 – Nov 13, 2026 (UTC). Net change +291 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/LingX-AI/LinkSense) Badge
[](https://awesomerepos.com/LingX-AI/LinkSense) Timeline
It gained stars on 24 of the 74 days recorded since Sep 1, 2026.
Its largest 7 days were Nov 7, 2026 to Nov 13, 2026: 238 stars.
In the 30 days to Nov 13, 2026 it got 242 stars, 476% more than in the 30 days before.
- Created on the Repository Host
- Release v0.3.10
- Release v0.3.11
- Release v0.3.12
- Release v0.3.13
- +30 stars in one day
- Reached 100 stars, 72 days after it was created
- Largest star day recorded: +136 stars
- Entered the Repository Index: +121 stars in 7 days
- +46 stars in one day
- Release v0.3.14
- 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 13, 2026 – Nov 14, 2026. Forks +1. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 14, 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 last read these facts from GitHub on Nov 14, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 1 task for the maintainers of LingX-AI/LinkSense.
Improve the Health Facts of the GitHub repository LingX-AI/LinkSense. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/LingX-AI/LinkSense. 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 changelog file at the root Fact: No changelog file at the root (GitHub, 2026-11-14). Rule: The root of the default branch has a file named CHANGELOG, CHANGES, HISTORY, NEWS, RELEASE, or RELEASES, with no extension or with .md, .markdown, .rst, .txt, or .adoc. Release notes on GitHub releases do not count. Task: Add CHANGELOG.md at the root of the default branch. Write one section for each published release, newest first, from the GitHub releases, the Git tags, and the commit history. Do not invent changes. If the project uses a release tool (for example Changesets, release-please, or semantic-release), configure it to update this file for each release. 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
3 of 4 checks-
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-13, 1 day ago. Source
-
Yes: Commits in the last 13 weeks
994 commits on the default branch in the last 13 weeks (GitHub, 2026-11-14). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 11 of the last 52 weeks (GitHub, 2026-11-14). Source
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 66
- 98
- 97
- 79
- 47
- 107
- 97
- 118
- 142
- 66
- 77
Releases
2 of 3 checks-
Yes: A release in the last 365 days
Newest release v0.3.14 on 2026-11-12, 2 days ago. 10 or more releases in the last 365 days. Source
-
Yes: The newest release tag is a semantic version
The newest release tag is v0.3.14. Source
-
No: A changelog file at the root
No changelog file at the root (GitHub, 2026-11-14).
Security practice
1 of 1 check-
Yes: A security policy
GitHub finds a security policy (GitHub, 2026-11-14). Source
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
3 of 3 checksObservations
Latest Observation, Nov 14, 2026: 283 stars, 60 forks, last push Nov 13, 2026, not archived. One of 2 Observations since Nov 13, 2026.