registry / rio-design-tokens / 0.0.1-security
rio-design-tokens@0.0.1-security
security holding package
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection found only metadata and a README for an npm security holding package, with no executable code or lifecycle hooks. The advisory URL is documentation text, not package runtime network behavior.
Static reason
No blocking static signals were detected.
Trigger
none
Impact
none observed
Mechanism
metadata-only security holding package
AI rationale
Static inspection found only metadata and a README for an npm security holding package, with no executable code or lifecycle hooks. The advisory URL is documentation text, not package runtime network behavior.
Evidence
package.jsonREADME.md
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
Evidence against
- package.json has only name/version/description/repository and no scripts, bin, main, dependencies, or entrypoints.
- README.md identifies this as an npm security holding package placeholder.
- Only package.json and README.md are present in the extracted package.
- Pattern search found no lifecycle hooks, process execution, credential access, filesystem mutation, dynamic code loading, or network code.
Behavioral surface
NoLicense
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 Low
LowNo License
Affected versions and remediation
This report applies to rio-design-tokens@0.0.1-security.
See all versions of rio-design-tokens for other recorded verdicts.
- Review the evidence and your use of rio-design-tokens@0.0.1-security 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.