Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for scientific researchers, AI agent developers, automation builders, AI-curious readers, and any developer wiring an AI coding agent to scientific workflows -- and who can pair PKU-YuanGroup/OpenAI4S with Python 3.10+ + uv (auto-installed via setup.sh) for the runtime surface, an LLM provider (Volcengine Ark plan/v3 for the 9.9 ¥/month Doubao entry tier; or any OpenAI / Anthropic / Gemini
Who should use it
Who should skip it
Skip PKU-YuanGroup/OpenAI4S unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
PKU-YuanGroup/OpenAI4S is tracked by RepoRadar as a mit open-source pure-stdlib code in the Code-as-Action Scientific Research Agent section. It was first seen on 2026-07-07 and last updated on 2026-07-07. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, PKU-YuanGroup/OpenAI4S is strongest on workflow potential (9.5) and novelty (9.0) and weakest on maturity (6.3) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned PKU-YuanGroup/OpenAI4S a composite score of 8.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The 63* / 6-fork repo is brand new (one week old) and at active maintenance but the persistent-kernel action space is a kernel-level primitive -- the consumer SHOULD review the kernel sandbox before deploying in a multi-user environment (the README's roadmap lists `OS-level sandbox parity (Seatbelt / bubblewrap + seccomp) for the local kernel` as a future direction; which means the local kernel is not yet OS-sandboxed); the 9.9 ¥/month Volcengine entry tier depends on the `ark` provider's `doubao-seed-2.0-pro` model and the `minimax-m3` / `minimax-m2.7` model ids listed under the `ark` plan provider are non-OpenAI standard model names not currently publicly released by the named provider (a fictional-model pattern; cycle 146 risk_flag refinement: non-sponsor context.