스킬 upstash-ratelimit-js

📦

upstash-ratelimit-js

Name: upstash-ratelimit-js
Author: upstash

콘텐츠 리비전 r1 안전 🌐 네트워크 접근🔑 환경 변수⚙️ 외부 명령어

Implement Upstash Rate Limits for JavaScript APIs

Serverless APIs need request limits that balance abuse prevention, latency, and Redis costs. This skill guides SDK integration, algorithm selection, and operational configuration with focused TypeScript examples.

지원: Claude Codex Code(CC)

🥉 77 브론즈

Maintain this Skill? Claim it 🥉 77 브론즈

내 에이전트로 설치

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

에이전트 요청

Review the Skillstore skill "upstash-ratelimit-js" from https://skillstore.io/skills/upstash-upstash-ratelimit-js.md and its manifest at https://skillstore.io/api/skills/upstash-upstash-ratelimit-js/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

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

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

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

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

테스트해 보기

"upstash-ratelimit-js" 사용 중입니다. Which algorithm should I use for a low-cost, single-region endpoint that tolerates boundary bursts?

예상 결과:

Fixed window fits these requirements because its documented Redis command count is lower than sliding window.
Requests near a window boundary can create bursts beyond the intended short-term rate.
Choose a stable identifier and test behavior across window transitions before deployment.

"upstash-ratelimit-js" 사용 중입니다. My edge deployment loses analytics updates and rarely benefits from the block cache. What should I check?

예상 결과:

Create the limiter or shared ephemeral cache outside the request handler so warm invocations can reuse blocked identifiers.
Pass the pending promise to the runtime background task mechanism so analytics and replication can finish.
Cold starts still begin with empty caches, so cache savings depend on runtime reuse and traffic patterns.

보안 감사

안전

v1 • 2026. 10. 29. 버전별 보고서 열기

All 14 static findings are false positives involving documentation prose, Markdown formatting, example addresses, or legitimate Redis configuration. No evidence found of prompt injection, unauthorized command execution, credential exfiltration, or malicious intent in the reviewed files. Application integrations still require Redis credentials and deliberate timeout and consistency policies.

스캔된 파일

544

분석된 줄 수

검토 항목

오탐 무시됨

위험 요인

🌐 네트워크 접근 (7)

algorithms.md:38 features.md:42 features.md:115 pricing-cost.md:26 SKILL.md:7 traffic-protection.md:22 traffic-protection.md:56

🔑 환경 변수 (2)

pricing-cost.md:112 pricing-cost.md:112

⚙️ 외부 명령어 (2)

SKILL.md:14 SKILL.md:21-32

가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.

감사자: codex

이 보고서 공유 및 인용

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

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/upstash-upstash-ratelimit-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-ratelimit-js/security.svg)](https://skillstore.io/skills/upstash-upstash-ratelimit-js?utm_source=security_passport_badge)

HTML 배지

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

임베드 카드

<iframe src="https://skillstore.io/embed/skills/upstash-upstash-ratelimit-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-ratelimit-js security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/upstash-upstash-ratelimit-js/audits/1

BibTeX 인용

@techreport{upstash-upstash-upstash-ratelimit-js-2026,
  author = {upstash},
  title = {upstash-ratelimit-js security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/upstash-upstash-ratelimit-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-ratelimit-js security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "upstash"
date-released: "2026-10-29"
url: "https://skillstore.io/skills/upstash-upstash-ratelimit-js/audits/1"
identifiers:
  - type: other
    value: "skillstore:upstash-upstash-ratelimit-js:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

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

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Throttle a serverless API

Add per-user limits to an API route and return a 429 response when the quota is exhausted.

Plan Redis capacity and costs

Compare algorithm command counts, cache behavior, and replication overhead before choosing a regional deployment strategy.

Configure abuse protection

Apply deny-list checks to client metadata and account for exact matching, cached blocks, and asynchronous IP list updates.

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

Start with a basic limiter

Show a TypeScript Upstash rate limiter allowing five requests per user every ten seconds. Explain Redis configuration and handling rejected requests without exposing secrets.

Choose an algorithm

Compare fixed window, sliding window, and token bucket for my API. Ask about burst tolerance, regional deployment, and Redis costs before recommending an algorithm.

Review edge runtime behavior

Review my edge rate limiter for cache placement, timeout behavior, analytics, and pending task completion. Identify integration gaps and propose changes using bundled SDK documentation.

Design tiered regional limits

Design limits for free and paid tenants across two regions. Compare prefixes, weighted requests, protection, and command costs, and explain consistency and dynamic-limit restrictions.

모범 사례

Check bundled SDK documentation and source before implementing version-sensitive options, and keep Redis credentials in server-side configuration.
Reuse limiters outside serverless handlers and complete pending background work through the runtime lifecycle.
Choose trusted identifiers and test rejection, timeout, and regional consistency behavior against your security requirements.

피하기

Treating timeout success or multi-region quotas as strict abuse prevention guarantees.
Creating a fresh ephemeral cache for every request and expecting persistent block caching.
Assuming deny lists support CIDR ranges or patterns, or omitting client metadata required by protection checks.

자주 묻는 질문

Does this skill run a rate limiting service?

No. It provides SDK guidance and examples. Your application must install the packages, configure Redis, and enforce the returned decisions.

Which languages and runtimes does it cover?

It covers JavaScript and TypeScript integration, including serverless and edge runtime considerations for platforms such as Vercel and Cloudflare.

Does it require credentials?

Working integrations require an Upstash Redis URL and token. Keep these credentials server-side and do not include real values in prompts.

Are requests always blocked when Redis is unavailable?

No. The documented timeout behavior permits requests when Redis is slow or unreachable. Evaluate this behavior before protecting sensitive endpoints.

Can I use dynamic limits across multiple regions?

The supplied documentation limits dynamic rates to single-region limiters. Multi-region operation also trades strict enforcement for global performance.

Can this skill estimate my Redis bill?

It explains command counts and cost drivers. Actual bills depend on traffic, cache reuse, enabled features, regional configuration, and current service pricing.