スキル 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.