pierrecomputer / pierre
pierre’s open source code
- Stars
- 6,520 stars
- Forks
- 277 forks
- Language
- TypeScript
- License
- APACHE-2.0
- Created
- Sep 19, 2025
- Last push
- Nov 8, 2026
- Updated
- Nov 8, 2026
Admitted to the Repository Index on Nov 7, 2026: +122 stars in 7 days.
Star History
185 days recorded, May 8, 2026 – Nov 8, 2026 (UTC). Net change +2,703 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/pierrecomputer/pierre) Badge
[](https://awesomerepos.com/pierrecomputer/pierre) Timeline
It gained stars on 183 of the 185 days recorded since May 8, 2026.
Its largest 7 days were Aug 1, 2026 to Aug 7, 2026: 372 stars.
In the 30 days to Nov 8, 2026 it got 292 stars, 178% more than in the 30 days before.
- Created on the Repository Host
- +118 stars in one day
- Reached 5,000 stars, 261 days after it was created
- Largest star day recorded: +196 stars
- +118 stars in one day
- Release highlights-v0.3.0
- Release diffs-v1.6.2
- Release diffs-v1.6.4
- Release diffs-v1.6.3
- Release highlights-v0.4.0
- Entered the Repository Index: +122 stars in 7 days
- 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 8, 2026 – Nov 9, 2026. Forks 0. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 9, 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 9, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 2 tasks for the maintainers of pierrecomputer/pierre.
Improve the Health Facts of the GitHub repository pierrecomputer/pierre. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/pierrecomputer/pierre. 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. The newest release tag is a semantic version Fact: The newest release tag is diffs-v1.7.0-beta.3. 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. 2. A changelog file at the root Fact: No changelog file at the root (GitHub, 2026-11-09). 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
4 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-08, 0 days ago. Source
-
Yes: Commits in the last 13 weeks
123 commits on the default branch in the last 13 weeks (GitHub, 2026-11-09). Source
-
Yes: Commits in 26 or more of the last 52 weeks
Commits in 52 of the last 52 weeks (GitHub, 2026-11-09). Source
- 24
- 18
- 8
- 41
- 34
- 8
- 6
- 1
- 11
- 11
- 10
- 14
- 13
- 20
- 6
- 17
- 9
- 24
- 16
- 29
- 31
- 19
- 30
- 76
- 30
- 23
- 24
- 39
- 19
- 21
- 41
- 53
- 38
- 33
- 50
- 24
- 25
- 20
- 14
- 1
- 7
- 15
- 11
- 7
- 10
- 10
- 7
- 12
- 5
- 23
- 9
- 6
Releases
1 of 3 checks-
Yes: A release in the last 365 days
Newest release diffs-v1.7.0-beta.3 on 2026-11-09, 0 days ago. 10 or more releases in the last 365 days. Source
-
No: The newest release tag is a semantic version
The newest release tag is diffs-v1.7.0-beta.3. Source
-
No: A changelog file at the root
No changelog file at the root (GitHub, 2026-11-09).
Security practice
1 of 1 check-
Yes: A security policy
GitHub finds a security policy (GitHub, 2026-11-09). Source
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
3 of 3 checksDependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
GitHub has no dependency graph for this repository (scanned on Nov 9, 2026).
2 scanned repositories name a package from this repository.
Uses (in the index) · 0
None.
Used by (in the index) · 2
-
npm: @pierre/theme
- Arize-ai/phoenix 12K
npm: @pierre/theme
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package . A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 9, 2026: 6,520 stars, 277 forks, last push Nov 8, 2026, not archived. One of 2 Observations since Nov 8, 2026.