replit / datacat
Self-hosted observability: metrics, logs, traces, dashboards and alerts. Stores data in PostgreSQL or ClickHouse. Accepts OpenTelemetry data.
- Stars
- 463 stars
- Forks
- 50 forks
- Language
- TypeScript
- License
- APACHE-2.0
- Created
- Nov 17, 2026
- Last push
- Nov 20, 2026
- Updated
- Nov 20, 2026
Why these Tags: an agent read the README and quoted it
- Observability platform from the description:
Self-hosted observability: metrics, logs, traces, dashboards and alerts.
- Application performance monitoring from the readme:
APM service catalog, trace explorer and waterfall
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 19, 2026: +159 stars in 7 days.
Star History
4 days recorded, Nov 17, 2026 – Nov 20, 2026 (UTC). Net change +471 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/replit/datacat) Badge
[](https://awesomerepos.com/replit/datacat) Timeline
It gained stars on each of the 4 days recorded since Nov 17, 2026.
- Created on the Repository Host
- +72 stars in one day
- Reached 100 stars, 1 day after it was created
- +164 stars in one day
- Entered the Repository Index: +159 stars in 7 days
- Largest star day recorded: +189 stars
- 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 20, 2026 – Nov 21, 2026. Forks +2. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 21, 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 21, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 1 task for the maintainers of replit/datacat.
Improve the Health Facts of the GitHub repository replit/datacat. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/replit/datacat. 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: No GitHub release (read on 2026-11-21). 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
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-20, 1 day ago. Source
-
Yes: Commits in the last 13 weeks
8 commits on the default branch in the last 13 weeks (GitHub, 2026-11-21). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 1 of the last 52 weeks (GitHub, 2026-11-21). 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
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 8
Releases
1 of 3 checks (1 without data)Security practice
1 of 1 check-
Yes: A security policy
GitHub finds a security policy (GitHub, 2026-11-21). Source
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
3 of 3 checksObservations
Latest Observation, Nov 21, 2026: 463 stars, 50 forks, last push Nov 20, 2026, not archived. One of 2 Observations since Nov 20, 2026.