ryugi-artifacts@1.15.2
Server and viewer for the Ryugi artifacts app
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe source inspection found no install-time attack or concrete malicious behavior; the scanner's similarity and coverage hints did not establish one. The manifest, CLI, server credential request and required high-finding paths were inspected, and the credential use observed was for the configured Ryugi cloud service.
Decision evidence
public snapshot- The manifest exposes a CLI and lists prepublishOnly as a build step; it has no install lifecycle hook.
- The CLI receives explicit command-line arguments, and its start behavior is selected by the start command.
- The server uses its configured cloud origin for artifact operations that include its Ryugi credentials.
- The inspected viewer chunks begin with module imports or KaTeX parser code, consistent with bundled application and library code.
Source & flagged code
14 flagged · loading sourcePackage contains a high-severity secret pattern.
dist/viewer/prod-BUf-ByWA.jsView on unpkg · L2Google API key in dist/viewer/prod-BUf-ByWA.js
dist/viewer/prod-BUf-ByWA.jsView on unpkg · L2This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
Findings
Affected versions and remediation
This report applies to ryugi-artifacts@1.15.2.
See all versions of ryugi-artifacts for other recorded verdicts.
- Review the evidence and your use of ryugi-artifacts@1.15.2 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.