meteor / react-packages
Meteor packages for a great React developer experience
- Stars
- 577 stars
- Forks
- 165 forks
- Language
- JavaScript
- License
- OTHER
- Created
- May 27, 2015
- Last push
- Nov 6, 2026
- Updated
- Nov 6, 2026
Admitted to the Repository Index on Nov 19, 2026: 577 stars on 2026-11-19.
Star History
85 days recorded, Aug 29, 2026 – Nov 21, 2026 (UTC). Net change +2 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add to a README
Copy the Markdown into the README of your repository to show the image there, with a link to this page.
-
Star History chart
[](https://awesomerepos.com/meteor/react-packages) -
Badge
[](https://awesomerepos.com/meteor/react-packages)
The images get new data one time each day. They follow the light or dark theme of the page that shows them.
To keep one theme, add ?theme=light or
?theme=dark to the address of the chart.
Timeline
It gained stars on 2 of the 85 days recorded since Aug 29, 2026.
Its largest 7 days were Aug 29, 2026 to Sep 4, 2026: 1 star.
It had 575 stars before Aug 29, 2026 and has 577 stars now: 423 fewer than 1,000.
- Created on the Repository Host
- Release [email protected]: v2.7.2 - React Meteor Data
- Largest star day recorded: +1 stars
- +1 stars in one day
- Latest push
- Entered the Repository Index: 577 stars on 2026-11-19
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 20, 2026 – Nov 22, 2026. Forks 0. AwesomeRepos saw a new push on 0 of 2 days.
- Nov 21, 2026: no new push
- Nov 22, 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
Maintenance
2 of 4 checks (2 without data)-
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-06, 15 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
0 of 3 checks (1 without data)-
No: A release in the last 365 days
Newest release [email protected] on 2024-01-10, 1047 days ago. 0 releases in the last 365 days. Source
-
No: The newest release tag is a semantic version
The newest release tag is [email protected]. 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 a licence file, but cannot name the licence. 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.
Copies a prompt for a coding agent. It has 2 tasks for the maintainers of meteor/react-packages.
Improve the Health Facts of the GitHub repository meteor/react-packages. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/meteor/react-packages. 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. A release in the last 365 days Fact: Newest release [email protected] on 2024-01-10, 1047 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. 2. The newest release tag is a semantic version Fact: The newest release tag is [email protected]. 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. 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
This section shows the packages that connect this repository to other repositories in the index.
The GitHub dependency graph of this repository names 48 direct packages (scanned on Nov 22, 2026). Packages from 20 other repositories in the index are among them.
No scanned repository names a package from this repository.
Uses (in the index) · 20
- react/react 253K
npm: react, react-dom
- airbnb/javascript 148K
npm: eslint-config-airbnb
- microsoft/TypeScript 112K
npm: typescript
-
npm: puppeteer
-
npm: @types/meteor, @types/react, @types/yauzl
- meteor/meteor 45K
npm: meteor-node-stubs
- babel/babel 44K
npm: @babel/runtime
- eslint/eslint 28K
npm: eslint
-
npm: @testing-library/react
-
npm: @typescript-eslint/eslint-plugin
Show all 20
-
npm: eslint-plugin-react
-
GitHub Actions: actions/checkout
- tsconfig/bases 7.9K
npm: @tsconfig/recommended
-
npm: eslint-plugin-import
- actions/cache 5.6K
GitHub Actions: actions/cache
-
npm: @testing-library/react-hooks
- mozilla/source-map 3.7K
npm: source-map
-
npm: eslint-plugin-jsx-a11y
-
npm: @testing-library/dom
- github/codeql-action 1.7K
GitHub Actions: github/codeql-action/analyze, github/codeql-action/init
Used by (in the index) · 0
None.
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package (checked on Nov 3, 2026). 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 22, 2026: 577 stars, 165 forks, last push Nov 6, 2026, not archived. One of 3 Observations since Nov 20, 2026.