스킬 upstash-redis-js

📦

upstash-redis-js

Name: upstash-redis-js
Author: upstash

콘텐츠 리비전 r1 높은 위험 ⚙️ 외부 명령어🔑 환경 변수⚡ 스크립트 포함🌐 네트워크 접근

Build Serverless Redis Features with Upstash

Serverless Redis work requires correct command patterns, serialization, expiration, and concurrency choices. This skill provides focused Upstash Redis guidance for implementation, migration, search, and optimization.

지원: Claude Codex Code(CC)

⚠️ 38 나쁨

Maintain this Skill? Claim it ⚠️ 38 나쁨

설치 전에 중지하고 확인을 요청하세요.

계획을 검토하고 파일을 변경하기 전에 사용자의 명시적 동의를 받으세요.

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "upstash-redis-js" from https://skillstore.io/skills/upstash-upstash-redis-js.md and its manifest at https://skillstore.io/api/skills/upstash-upstash-redis-js/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/upstash-upstash-redis-js.md 서명된 manifest GET /api/skills/upstash-upstash-redis-js/manifest 서명된 lockfile GET /api/skills/upstash-upstash-redis-js/lockfile

테스트해 보기

"upstash-redis-js" 사용 중입니다. Create a cache for user profiles with a one-hour lifetime.

예상 결과:

A cache-aside design with namespaced keys, one-hour expiration, database fallback, and explicit invalidation after profile updates.

"upstash-redis-js" 사용 중입니다. Reduce latency for fetching profile data for many users.

예상 결과:

A pipeline strategy that batches related reads, preserves result ordering, and defines handling for partial failures.

"upstash-redis-js" 사용 중입니다. Add product search with price and category filters.

예상 결과:

An Upstash Redis Search plan covering schema fields, exact category matching, numeric price filters, pagination, and index readiness.

보안 감사

높은 위험

v1 • 2026. 8. 25. 버전별 보고서 열기

Most static findings are false positives caused by JavaScript template literals, Redis pipeline exec methods, environment-based configuration, and search keyword fields. One static network finding is confirmed because the skill directs agents to provision an external database. Semantic review also found an authentication bypass placeholder and an unsafe simple lock-release example.

스캔된 파일

3,810

분석된 줄 수

검토 항목

오탐 무시됨

확인된 보안 우려 사항 (3)

높음

patterns/session-management.md:214-216

Authentication Placeholder Accepts Every Login

The verifyCredentials helper returns a user for every email and password. Copying this example into an application would create a complete authentication bypass.

The helper unconditionally returns a user object and never checks the password. The placeholder label is clear, but the executable example remains unsafe if adopted.

중간

SKILL.md:42

External Database Provisioning Lacks Confirmation

The skill tells an agent to create a temporary Upstash database when credentials are absent. It does not require explicit user approval before the external POST.

The instruction explicitly targets agents and describes a POST that creates a database. No confirmation or consent boundary appears in the instruction.

중간

patterns/distributed-locks.md:38-39 patterns/distributed-locks.md:53-57

Simple Lock Release Can Delete Another Owner's Lock

The simple release function deletes a lock without verifying ownership. An expired and reacquired lock can be removed by the previous worker.

The finally block always calls redis.del through releaseLock. The same guide later provides token-checked release logic, confirming ownership validation is required.

기능 검토 항목 (1)

이 스킬에 대해 예상될 수 있는 실제 로컬 기능이므로 검토가 필요하지만, 확인된 악의적 동작으로는 집계되지 않습니다.

낮음

SKILL.md:42

Hardcoded URL

> **No credentials yet?** If you're an agent that needs scratch Redis and the user hasn't provided a

The text directs an agent to POST to an Upstash endpoint that creates a temporary database. This is a real external side effect without an explicit user-confirmation step.

위험 요인

⚙️ 외부 명령어 (50)

🔑 환경 변수 (42)

⚡ 스크립트 포함 (15)

advanced-features/pipeline-and-transactions.md:33 advanced-features/pipeline-and-transactions.md:42 advanced-features/scripting.md:35 migrations/from-ioredis.md:119 migrations/from-ioredis.md:130 migrations/from-redis-node.md:159 migrations/from-redis-node.md:169 patterns/leaderboard.md:121 patterns/session-management.md:152 patterns/session-management.md:204 performance/batching-operations.md:61 performance/pipeline-optimization.md:56 performance/pipeline-optimization.md:70 performance/pipeline-optimization.md:77 performance/pipeline-optimization.md:95

🌐 네트워크 접근 (6)

SKILL.md:38 SKILL.md:42 SKILL.md:181 SKILL.md:182 SKILL.md:183 SKILL.md:184

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/upstash-upstash-redis-js/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/upstash-upstash-redis-js/security.svg)](https://skillstore.io/skills/upstash-upstash-redis-js?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/upstash-upstash-redis-js?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/upstash-upstash-redis-js/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/upstash-upstash-redis-js.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

학술 인용 (APA · BibTeX · CFF)

APA 인용

upstash. (2026). upstash-redis-js security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/upstash-upstash-redis-js/audits/1

BibTeX 인용

@techreport{upstash-upstash-upstash-redis-js-2026,
  author = {upstash},
  title = {upstash-redis-js security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/upstash-upstash-redis-js/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "upstash-redis-js security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "upstash"
date-released: "2026-08-25"
url: "https://skillstore.io/skills/upstash-upstash-redis-js/audits/1"
identifiers:
  - type: other
    value: "skillstore:upstash-upstash-redis-js:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Add Application Caching

Design cache keys, expiration rules, serialization, and invalidation for a TypeScript service.

Optimize Redis Traffic

Choose batching, pipelines, transactions, retries, and timeouts for serverless workloads.

Plan a Redis Migration

Translate node-redis or ioredis usage into Upstash Redis patterns and identify behavior changes.

이 프롬프트를 사용해 보세요

Create a Redis Client

Show how to configure Upstash Redis in my [framework] project using environment variables and TypeScript.

Implement a Cache

Design a cache-aside flow for [data type] with key naming, TTL, invalidation, and error handling.

Migrate a Redis Module

Convert my [node-redis or ioredis] module to Upstash Redis and explain serialization, pipelines, and connection changes.

Design Atomic Redis Logic

Design an atomic [workflow] using transactions or Lua, with concurrency assumptions, failure cases, and production safeguards.

모범 사례

Keep Redis credentials in environment variables and never place tokens in source code.
Namespace keys and apply expiration rules that match each data lifecycle.
Use token-checked locks and production libraries for concurrency-sensitive workflows.

피하기

Do not treat all Redis values as strings when native serialization is available.
Do not use unbounded keys or sessions without expiration and cleanup rules.
Do not provision external resources or execute destructive commands without explicit user confirmation.