Home/AionUi/Trust report

Trust and health report

AionUi - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated 4d · GitHub synced 4d

Maintenance

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Very active96% signal

last push 2d ago · last release 6d · 30 releases (90d)

+1.8k stars (30d) · +129 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

Security intelligence

Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.

OSV dependency advisories

No lockfile (source not queried)
Last query
1mo
Scanner
osv@v1
View source evidence

deps.dev advisories

Not queried
Scanner
deps.dev@v1
View source evidence

OpenSSF Scorecard

Not queried
Scanner
openssf-scorecard@v1

Weekly public scans omit some checks at scale.

View source evidence

Method and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/iofficeai-aionui/trust.

Common questions

Is AionUi maintained?
GraphCanon rates AionUi "Very active" (96% maintenance signal from public GitHub metadata, computed 4d). Last push was 2 days ago. 30 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
Is AionUi safe to use?
Last scanned 1mo (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits. GraphCanon does not certify AionUi as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is AionUi a fork?
No. AionUi is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does AionUi have known security vulnerabilities?
Last scanned 1mo (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits.
How often is the AionUi trust report updated?
Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 4d (methodology github_public_v1).
What does GraphCanon never claim about AionUi?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for AionUi. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for AionUi?
Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology for full scope and limits.

Was this helpful?

Anonymous feedback helps us improve pages and translations.