pydantic / monty
A secure Python sandbox, written in Rust, for code written by AI.
- Stars
- 8,890 stars
- Forks
- 492 forks
- Language
- Rust
- License
- MIT
- Created
- May 28, 2023
- Last push
- Nov 11, 2026
- Updated
- Nov 11, 2026
Why these Tags: an agent read the README and quoted it
- Agent sandbox from the description:
A secure Python sandbox, written in Rust, for code written by AI.
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 10, 2026: 8,874 stars on 2026-11-10.
Star History
188 days recorded, May 8, 2026 – Nov 11, 2026 (UTC). Net change +1,879 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/pydantic/monty) Badge
[](https://awesomerepos.com/pydantic/monty) Timeline
It gained stars on 187 of the 188 days recorded since May 8, 2026.
Its largest 7 days were Jun 9, 2026 to Jun 15, 2026: 374 stars.
In the 30 days to Nov 11, 2026 it got 288 stars, 34% fewer than in the 30 days before.
It had 7,011 stars before May 8, 2026 and has 8,890 stars now: 1,110 fewer than 10,000.
- Created on the Repository Host
- +125 stars in one day
- Largest star day recorded: +131 stars
- +106 stars in one day
- Release v1.2.0: v1.2.0 - 2026-10-18
- Release v1.3.0: v1.3.0 - 2026-10-21
- Release 1.4.0: v1.4.0 - 2026-10-26
- Release v1.5.0: v1.5.0 - 2026-11-05
- Entered the Repository Index: 8,874 stars on 2026-11-10
- Release v1.6.0: v1.6.0 - 2026-11-11
- 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 11, 2026 – Nov 12, 2026. Forks +2. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 12, 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 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-11, 0 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
2 of 3 checks (1 without data)-
Yes: A release in the last 365 days
Newest release v1.6.0 on 2026-11-11, 1 day 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 v1.6.0. 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 the licence MIT. 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.
Dependencies 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 12, 2026).
9 scanned repositories name a package from this repository.
Uses (in the index) · 0
None.
Used by (in the index) · 9
-
PyPI: pydantic-monty
-
PyPI: pydantic-monty
-
PyPI: pydantic-monty
- Arize-ai/phoenix 12K
PyPI: pydantic-monty
-
npm: @pydantic/monty, @pydantic/monty-darwin-arm64, @pydantic/monty-darwin-x64, @pydantic/monty-linux-arm64-gnu and 2 more
PyPI: pydantic-monty
-
PyPI: pydantic-monty
- kirodotdev/KiroCrew 4.9K
npm: @pydantic/monty-darwin-arm64, @pydantic/monty-darwin-x64, @pydantic/monty-linux-arm64-gnu, @pydantic/monty-linux-x64-gnu and 1 more
PyPI: pydantic-monty, pydantic-monty-client, pydantic-monty-runtime
-
Cargo: monty, monty-macros, monty-types
-
npm: @pydantic/monty, @pydantic/monty-darwin-arm64, @pydantic/monty-darwin-x64, @pydantic/monty-linux-arm64-gnu and 2 more
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 12, 2026: 8,890 stars, 492 forks, last push Nov 11, 2026, not archived. One of 2 Observations since Nov 11, 2026.