registry / tinkoff-cache-path / 0.0.0-stage
tinkoff-cache-path@0.0.0-stage
Temporary package placeholder for staged publishing
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected package contains only a manifest and README placeholder, with no declared install hooks or runtime entrypoints. The source review found no attack behavior.
Static reason
No blocking static signals were detected.
Trigger
None identified.
Impact
No package-driven harmful effect was identified.
Mechanism
No executable package behavior was declared in the manifest.
AI rationale
The inspected package contains only a manifest and README placeholder, with no declared install hooks or runtime entrypoints. The source review found no attack behavior.
Decision evidence
public snapshotAI called this Clean at 99.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest contains only package metadata and a stub marker; it declares no lifecycle hooks or runtime entrypoints.
Evidence against
Behavioral surface
NoLicense
Source & flagged code
1 flagged · loading sourcepackage.jsonView file
1{
"name": "tinkoff-cache-path",
"version": "0.0.0-stage",
"stub": true,
"description": "Temporary package placeholder for staged publishing"
}
Low
Suspicious Lifecycle Evidence
The manifest contains only package metadata and a stub marker; it declares no lifecycle hooks or runtime entrypoints.
package.jsonView on unpkg · L1Findings
2 Low
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to tinkoff-cache-path@0.0.0-stage.
See all versions of tinkoff-cache-path for other recorded verdicts.
- Review the evidence and your use of tinkoff-cache-path@0.0.0-stage 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.