Skip to content
Back to skills

V1.0.2

ASecurity

Upgrade a project to forge v1.0.2. (1) pkg/servicecatalog.MaxBytes is removed — a service catalog has no size bound of its own; the reader that fetched the bytes owns the bound (release.ManifestsLayerMaxBytes for a bundle layer). Use when Go code names servicecatalog.MaxBytes.

  • 10 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added November 13, 2026
ai-agentsgonode

Security analysis

A100/100

Scanned November 13, 2026

npx -y skills add reliant-labs/forge --skill v1.0.2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of V1.0.2?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for V1.0.2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/reliant-labs-v1-0-2/badge)](https://www.skillsdirectory.com/skills/reliant-labs-v1-0-2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: v1.0.2
description: Upgrade a project to forge v1.0.2. (1) pkg/servicecatalog.MaxBytes is removed — a service catalog has no size bound of its own; the reader that fetched the bytes owns the bound (release.ManifestsLayerMaxBytes for a bundle layer). Use when Go code names servicecatalog.MaxBytes.
version: v1.0.2
detection: grep -rqsE --include='*.go' --exclude-dir=gen --exclude-dir=vendor --exclude-dir=node_modules 'servicecatalog\.MaxBytes' . && exit 0; exit 1
---

# Upgrading to v1.0.2

Each section below is independent: apply the ones whose "Use when" matches.

## 1. `servicecatalog.MaxBytes` is removed

**Use when** Go code names `servicecatalog.MaxBytes`.

**What changed.** The 1 MiB cap refused real projects (reliant's catalog is
2.1 MB compact) and bounded bytes already in memory. `servicecatalog.Decode`
now validates shape only. A catalog in a bundle is a manifests-layer artifact,
bounded like every other artifact by `release.ManifestsLayerMaxBytes`.

**What to do.** Bound the READ that fetches the catalog, not the decode:

- reading it from a bundle layer: `release.ValidateManifestsLayer` /
  `release.ReadSnapshotAssets` already apply the layer bound — delete your check;
- reading it from anywhere else (a registry blob, a request body): bound that
  read with the limit of the thing you read it from, e.g.
  `io.LimitReader(r, release.ManifestsLayerMaxBytes+1)`;
- returning it in a response: fit it to your server's send limit
  (`connect.WithSendMaxBytes`), not to a catalog constant.

A decision about which bound applies is yours to make, so there is no codemod.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.