← Home

redoc

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

romanhotsiy

Keywords

OpenAPIOpenAPI SpecificationSwaggerJSON-SchemaAPIRESTdocumentationReact.js

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from personal account to GitHub Actions CI/CD; SLSA provenance confirms legitimate pipeline. ai
provenance slsa-provenance AI (provenance): Valid SLSA attestation; stable signal for this package. ai
dependencies unvetted-dep:stickyfill AI (dependencies): stickyfill has been a dependency of redoc for years; polyfill for position:sticky. ai
typosquat typosquat.levenshtein:redux AI (typosquat): redoc is a well-known brand (Redocly), not a typosquat of redux. ai
phantom-deps phantom-dep:swagger2openapi AI (phantom-deps): Referenced in config/build tooling, not direct import — stable false positive for this package. ai
typosquat typosquat.levenshtein:redis AI (typosquat): redoc is a well-known brand (Redocly), not a typosquat of redis. ai
phantom-deps phantom-dep:path-browserify AI (phantom-deps): Used as webpack browser polyfill via config, not direct import — stable false positive. ai

Versions (showing 3 of 3)

Version Deps Published
2.5.3 21 / 68
2.5.2 21 / 68
2.5.1 21 / 68

v2.5.3

2 findings
HIGH Publisher changed: romanhotsiy → GitHub Actions (on 2026-05-29) provenance

This version was published by a different npm account than previous versions on 2026-05-29. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.