Nagisanzenin Engram
Evidence-based learning engine — first-principles curricula, free-recall verification with receipts, FSRS-scheduled memory, and explorable artifacts. Learn anything; keep it.
Is Nagisanzenin Engram safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Nagisanzenin Engram
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Nagisanzenin Engram scores 53.2/100 (Grade C), ranked #191 of 351 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.7/10; 1% of recent commits are signed; last pushed 2026-08-27. Every point is earned from checkable signals — never paid placement. How scoring works →
How Nagisanzenin Engram compares in Agent Skills
- #189 Power Bi Agentic Development 53.3 +0.1
- #190 Video Shotcraft 53.3 +0.1
- #191 Nagisanzenin Engram 53.2 this agent
- #192 Baoyu Design 52.9 −0.3
- #193 Slides Maker 52.9 −0.3
Bars show each HVTrust score; the tick marks Nagisanzenin Engram’s 53.2.
Where the 53.2 comes from
HVTrust dimensions vs the Agent Skills average
53.2 / 100 · 100.0% confidenceNagisanzenin Engram Agent Skills average (351 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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
61.2 / 100Supply Chain Trust
Common questions about Nagisanzenin Engram
Does Nagisanzenin Engram publish package provenance?
Does Nagisanzenin Engram have an OpenSSF Scorecard?
Is Nagisanzenin Engram actively maintained?
What license does Nagisanzenin Engram use?
Are Nagisanzenin Engram'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 Nagisanzenin Engram'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 Nagisanzenin Engram?
For maintainers
HVTrust scores Nagisanzenin Engram 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/nagisanzenin-engram)
<a href="https://hvtracker.net/agents/nagisanzenin-engram"><img src="https://hvtracker.net/badge/nagisanzenin-engram.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON