yandex / porto
Yet another Linux container management system
- Stars
- 403 stars
- Forks
- 50 forks
- Language
- C++
- License
- OTHER
- Created
- Aug 27, 2015
- Last push
- Jan 20, 2023
- Updated
- Oct 21, 2026
- Status
- Archived
Why these Tags: an agent read the README and quoted it
- Container runtime from the readme:
Porto is a yet another Linux container management system, developed by Yandex.
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.
In the Repository Index since Oct 22, 2026.
Star History
162 days recorded, May 31, 2026 – Nov 8, 2026 (UTC). Net change +1 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/yandex/porto) Badge
[](https://awesomerepos.com/yandex/porto) Timeline
It gained stars on 1 of the 162 days recorded since May 31, 2026.
Its largest 7 days were May 31, 2026 to Jun 6, 2026: 1 star.
It had 402 stars before May 31, 2026 and has 403 stars now: 97 fewer than 500.
It was archived before Oct 22, 2026, the day of its first Observation.
- Created on the Repository Host
- Latest push
- Largest star day recorded: +1 stars
- Entered the Repository Index
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 19 Observations, Oct 22, 2026 – Nov 9, 2026. Forks 0. AwesomeRepos saw a new push on 0 of 18 days.
- Oct 23, 2026: no new push
- Oct 24, 2026: no new push
- Oct 25, 2026: no new push
- Oct 26, 2026: no new push
- Oct 27, 2026: no new push
- Oct 28, 2026: no new push
- Oct 29, 2026: no new push
- Oct 30, 2026: no new push
- Oct 31, 2026: no new push
- Nov 1, 2026: no new push
- Nov 2, 2026: no new push
- Nov 3, 2026: no new push
- Nov 4, 2026: no new push
- Nov 5, 2026: no new push
- Nov 6, 2026: no new push
- Nov 7, 2026: no new push
- Nov 8, 2026: no new push
- Nov 9, 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
Copies a prompt for a coding agent. It has 1 task for the maintainers of yandex/porto.
Improve the Health Facts of the GitHub repository yandex/porto. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/yandex/porto. 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-08). 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
0 of 4 checks (2 without data)-
No: Not archived
GitHub marks the repository as archived. Source
-
No: A push in the last 90 days
Last push on 2023-01-20, 1389 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 (2 without data)-
No: A release in the last 365 days
No GitHub release (read on 2026-11-08). Source
-
No data: The newest release tag is a semantic version
No data: no release.
-
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.
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 52 direct packages (scanned on Nov 5, 2026). Packages from 11 other repositories in the index are among them.
No scanned repository names a package from this repository.
Uses (in the index) · 11
-
Go: k8s.io/kubernetes
- sirupsen/logrus 26K
Go: github.com/sirupsen/logrus
- uber-go/zap 25K
Go: go.uber.org/zap
- grpc/grpc-go 23K
Go: google.golang.org/grpc
-
Go: github.com/containerd/containerd
- json-iterator/go 14K
Go: github.com/json-iterator/go
-
Go: github.com/golang/groupcache
- golang/protobuf 10K
Go: github.com/golang/protobuf
- davecgh/go-spew 6.4K
Go: github.com/davecgh/go-spew
- emicklei/go-restful 5.1K
Go: github.com/emicklei/go-restful/v3
Show all 11
- uber-go/multierr 1.2K
Go: go.uber.org/multierr
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 9, 2026: 403 stars, 50 forks, last push Jan 20, 2023, archived. One of 19 Observations since Oct 22, 2026.