contentlayerdev / contentlayer

Star History

185 days recorded, May 12, 2026 – Nov 12, 2026 (UTC). Net change +19 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

[![Star History of contentlayerdev/contentlayer](https://awesomerepos.com/contentlayerdev/contentlayer/stars.svg)](https://awesomerepos.com/contentlayerdev/contentlayer) Copy

Badge

[![AwesomeRepos](https://awesomerepos.com/contentlayerdev/contentlayer/badge.svg)](https://awesomerepos.com/contentlayerdev/contentlayer) Copy

Timeline

1. Jan 20, 2021 Created on the Repository Host
2. Jan 18, 2023 Release v0.3.0
3. Mar 28, 2023 Release v0.3.1
4. Apr 24, 2023 Release v0.3.2
5. May 31, 2023 Release v0.3.3
6. Jun 29, 2023 Release v0.3.4
7. Nov 7, 2024 Latest push
8. May 14, 2026 Largest star day recorded: +1 stars
9. May 22, 2026 +1 stars in one day
10. Jun 10, 2026 +1 stars in one day
11. Nov 10, 2026 Entered the Repository Index: 3,536 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 3 Observations, Nov 11, 2026 – Nov 13, 2026. Forks 0. AwesomeRepos saw a new push on 0 of 2 days.

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

Improve the Health Facts of the GitHub repository contentlayerdev/contentlayer.

AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/contentlayerdev/contentlayer. 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 v0.3.4 on 2023-06-29, 1232 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

Dependencies in the index

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 13, 2026: 3,535 stars, 190 forks, last push Nov 7, 2024, not archived. One of 3 Observations since Nov 11, 2026.