All 99 static findings are false positives caused by Markdown fences, TypeScript template literals, placeholders, or legitimate NEAR development documentation. The reviewed materials contain no embedded credentials, prompt-injection text, unauthorized command execution, or evidence of data exfiltration. Key-handling examples should still be used only with protected server-side secrets.
The skill is documentation for near-kit and I found no prompt injection or malware intent. Most static hits are false positives from Markdown fences, TypeScript template strings, placeholder URLs, and local example APIs. Key handling examples and ~/.near-credentials access are real sensitive-use risks that need stronger warnings.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
import { Near, generateSeedPhrase, parseSeedPhrase } from "near-kit";
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
validatePrivateKey("ed25519:..."); // throws if invalid
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
const near = new Near({ network: "testnet", privateKey: "..." })
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
import { Near, fromHotConnect, fromWalletSelector, type WalletConnection, type PrivateKey } from "ne
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
import { generateKey, parseSeedPhrase, generateSeedPhrase } from "near-kit";
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation demonstrates private key or key validation patterns for signing. The examples use placeholders, but the guidance still involves sensitive wallet credentials.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
// generateSeedPhrase() returns a string (just the phrase)
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
// parseSeedPhrase() returns a KeyPair-like object
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
The documentation teaches seed phrase generation or parsing, which handles wallet recovery secrets. Even with placeholders, this requires high-care secret handling guidance.
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
keyStore: new FileKeyStore("~/.near-credentials", "mainnet"),
The documentation uses FileKeyStore with ~/.near-credentials, a hidden home-directory credential store. That path can contain wallet keys, so the access pattern is a real sensitive-filesystem risk.
keyStore: new FileKeyStore("~/.near-credentials", "mainnet"),
The documentation uses FileKeyStore with ~/.near-credentials, a hidden home-directory credential store. That path can contain wallet keys, so the access pattern is a real sensitive-filesystem risk.
keyStore: new FileKeyStore("~/.near-credentials", "testnet"),
The documentation uses FileKeyStore with ~/.near-credentials, a hidden home-directory credential store. That path can contain wallet keys, so the access pattern is a real sensitive-filesystem risk.
keyStore: new FileKeyStore("~/.near-credentials", "testnet"),
The documentation uses FileKeyStore with ~/.near-credentials, a hidden home-directory credential store. That path can contain wallet keys, so the access pattern is a real sensitive-filesystem risk.