Novel To Game
Website
把小说改编成可玩游戏的 AI skill 合集：从文字冒险、策略经营到互动影游，一站式生成策划案、可运行代码与实机验收，适配 Claude Code / Codex 等 ｜ Agent skills for adapting novels into playable games
Is Novel To Game safe? Promising trust profile, but some evidence still deserves review.
Compare Novel To Game
How does it stack up against its Agent Skills neighbours?
- Aaron Marketing Skills +0.1 higher
- Power Bi Agentic Development +0.1 higher
- Claude Codex Settings same score
In detail: Novel To Game scores 56.1/100 (Grade C), ranked #161 of 384 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 34% of recent commits are signed; last pushed 2026-11-08. Every point is earned from checkable signals — never paid placement. How scoring works →
How Novel To Game could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 5.0 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Dependency-Update-Tool 0 +8.3 → 64.4 C · #68 of 384
- Sign every commit34% signed today +3.2 → 59.3 C · #117 of 384
Chain of custody
Scanners check what the code says. This traces who ships Novel To Game and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.
-
Source Partly signed
github.com/zenstory-ai/novel-to-game, MIT, last pushed 2026-11-08. 34% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.0/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies10
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 3Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 10SAST 0Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 10 -
Published packages None
No registry package. Novel To Game is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
- 2026-08-30 OSSF Scorecard: 4.5/10
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Novel To Game’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.
How Novel To Game compares in Agent Skills
- #159 Aaron Marketing Skills 56.2 +0.1
- #160 Power Bi Agentic Development 56.2 +0.1
- #161 Novel To Game 56.1 this agent
- #162 Claude Codex Settings 56.1 ±0
- #163 Baoyu Design 55.9 −0.2
Bars show each HVTrust score; the tick marks Novel To Game’s 56.1.
Where the 56.1 comes from
HVTrust dimensions vs the Agent Skills average
56.1 / 100 · 100.0% confidenceNovel To Game Agent Skills average (384 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
70.7 / 100Common questions about Novel To Game
Does Novel To Game publish package provenance?
Does Novel To Game have an OpenSSF Scorecard?
Is Novel To Game actively maintained?
What license does Novel To Game use?
Are Novel To Game's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Novel To Game's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Novel To Game?
For maintainers
HVTrust scores Novel To Game from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/novel-to-game)
<a href="https://hvtracker.net/agents/novel-to-game"><img src="https://hvtracker.net/badge/novel-to-game.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON