ryugi-artifacts@1.13.1
Server and viewer for the Ryugi artifacts app
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected source supports ordinary viewer, project-server, and explicit CLI configuration behavior. Scanner flags for process execution, secrets, and invisible Unicode did not establish an attack: the process calls serve CLI operations, the frontend strings include public service configuration, and the flagged file is a localized UI bundle.
Decision evidence
public snapshot- The package has a prepublishOnly build hook, with no install-time lifecycle hook in its manifest.
- The CLI starts its bundled server when invoked and stores its state under the selected project’s .ryugi/artifacts directory.
- Agent environment markers are recorded to the project’s server state; auto-publish configuration changes only when the CLI receives the corresponding option.
- The viewer bundles reference Excalidraw services and frontend modules; the flagged language file contains localized interface strings.
Source & flagged code
8 flagged · loading sourcePackage contains a high-severity secret pattern.
dist/viewer/prod-CxvgXXgp.jsView on unpkg · L2Google API key in dist/viewer/prod-CxvgXXgp.js
dist/viewer/prod-CxvgXXgp.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to ryugi-artifacts@1.13.1.
See all versions of ryugi-artifacts for other recorded verdicts.
- Review the evidence and your use of ryugi-artifacts@1.13.1 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.