All status pages · Unowned issues across all projects · How to write a weekly status report from GitHub

Weekly status: nestjs/nest

2026-10-14 to 2026-10-20 (7 full days, UTC). Unofficial: generated from this repository’s public GitHub activity by pilotless status. Not affiliated with the project, and no information here that GitHub does not publish.

182 commits to master by 16 people, 49 pull requests merged, 21 open pull requests, 7 open issues on this page of results.

Stalled pull requests

Open, and untouched for seven days or more:

#16231 build: replace deprecated coveralls with supported coveralls-next - last touched 62 days ago
#17874 fix(common): reject unsafe integers in ParseIntPipe - last touched 26 days ago
#14359 feat(common): add new flatten options to validation pipe - last touched 26 days ago
#14470 feat(platform-fastify): add fastify custom log level feature - last touched 25 days ago
#16966 feat(common): allow injecting global serializer options - last touched 25 days ago

Issues nobody has picked up

Open, unassigned, and with no replies yet:

#4944 Dependency Dashboard - opened 2311 days ago

The two lists above are what a status meeting is usually for. Nobody had to attend one to produce this page.

If you maintain nestjs/nest and would rather this page did not exist, open an issue and it will be deleted - no argument, no reply needed beyond the repository name.

Want this for your own repositories? Install the pilotless GitHub App — one click, then a pinned weekly status digest in each selected repo. Prefer CI-only? The status-action is still two lines of YAML with no account and nothing leaving GitHub.