ryugi-artifacts@1.18.4
Server and viewer for the Ryugi artifacts app
AI Security Review
scanned 15h ago · by lpm-firewall-aiSource inspection found no install-time attack or unrelated credential transfer. The scanner’s similarity and Unicode flags do not establish malicious behavior: the cited viewer files are bundled application code, and the flagged translation file showed no searched bidi controls.
Decision evidence
public snapshot- package.json defines `prepublishOnly` as a build step, and the executable routes user invocation to the CLI.
- The flagged viewer files contain bundled UI and rendering code; the flagged Kurdish file contains UI translations, with no searched bidi controls found.
- The server sends saved credentials to its configured Ryugi cloud origin for application requests; the default origin is `https://ryugi.innei.dev`.
- The CLI processes arguments supplied by the user, and the viewer calls a same-origin cloud API.
Source & flagged code
10 flagged · loading sourceSource spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
dist/cli.cjsView on unpkg · L26Findings
Affected versions and remediation
This report applies to ryugi-artifacts@1.18.4.
See all versions of ryugi-artifacts for other recorded verdicts.
- Review the evidence and your use of ryugi-artifacts@1.18.4 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.