You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The facts behind them hold: the repo is public (MIT, 31 stars, default branch main), npm tiny-oss@1.1.0 is published with engines.node: ^20.19.0 || >=22.12.0, and .github/workflows/ci.yml (name CI) exists.
Proposed implementation for the feature run: one badge row directly under the # tiny-oss heading, keeping the existing npm-version badge and adding downloads, license, CI status, bundle size and Node — mirrored into README_zh-CN.md for parity. Commit type docs; no source or dependency change.
The only open point is the exact set/order and whether to mirror the Chinese README. That is a normal PR-review adjustment rather than a blocking question, so this is ready-for-agent rather than needs-info. No bug label, so the next stage is feature.
Added the common README badges under the # tiny-oss heading in both README.md and README_zh-CN.md (parity), keeping the existing npm-version badge and adding downloads, license, CI status, bundle size and Node. Docs-only change (docs commit): no source, dependency or workflow file touched.
Every badge image URL and link target was verified HTTP 200 from the runner, and all verify gates pass (pnpm lint, pnpm fmt:check, pnpm build, pnpm check:types, pnpm test:azure-oracle, headless browser suite 22 files / 231 passed).
Activity
github-actions commentedon Sep 17, 2026
Loop triage —
feature/ready-for-agent(confidence: medium)Issue #54 asks for the common badges in the README. Today there is exactly one badge, and only in the English file:
README.md:3—[](https://www.npmjs.com/package/tiny-oss)README_zh-CN.md— no badge row at all.I checked that every conventional badge is valid for this package/repo — all of these return HTTP 200:
https://img.shields.io/npm/v/tiny-osshttps://img.shields.io/npm/dm/tiny-osshttps://img.shields.io/npm/l/tiny-osshttps://img.shields.io/bundlephobia/minzip/tiny-osshttps://img.shields.io/node/v/tiny-osshttps://github.com/Alex1990/tiny-oss/actions/workflows/ci.yml/badge.svgThe facts behind them hold: the repo is public (MIT, 31 stars, default branch
main), npmtiny-oss@1.1.0is published withengines.node: ^20.19.0 || >=22.12.0, and.github/workflows/ci.yml(nameCI) exists.Proposed implementation for the
featurerun: one badge row directly under the# tiny-ossheading, keeping the existing npm-version badge and adding downloads, license, CI status, bundle size and Node — mirrored intoREADME_zh-CN.mdfor parity. Commit typedocs; no source or dependency change.The only open point is the exact set/order and whether to mirror the Chinese README. That is a normal PR-review adjustment rather than a blocking question, so this is
ready-for-agentrather thanneeds-info. Nobuglabel, so the next stage isfeature.github-actions commentedon Sep 17, 2026
Loop feature — PR opened for this.
Added the common README badges under the
# tiny-ossheading in bothREADME.mdandREADME_zh-CN.md(parity), keeping the existing npm-version badge and adding downloads, license, CI status, bundle size and Node. Docs-only change (docscommit): no source, dependency or workflow file touched.Every badge image URL and link target was verified HTTP 200 from the runner, and all verify gates pass (
pnpm lint,pnpm fmt:check,pnpm build,pnpm check:types,pnpm test:azure-oracle, headless browser suite 22 files / 231 passed).docs: replace broken bundlephobia badge with bundlejs