@redocly/redoc-reef
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@opentelemetry/api | AI (phantom-deps): OpenTelemetry packages loaded via config; stable pattern for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package; missing description is common and low-risk. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped package loaded by convention in build pipeline. | ai | |
| phantom-deps | phantom-dep:babel-plugin-styled-components | AI (phantom-deps): Babel plugin loaded via config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@redocly/portal-plugin-mock-server | AI (phantom-deps): Same-org scoped package; likely loaded by convention. | ai | |
| dependencies | unvetted-dep:@redocly/openapi-docs | AI (dependencies): Same org scope; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:@redocly/asyncapi-docs | AI (dependencies): Same org scope; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:@redocly/portal-legacy-ui | AI (dependencies): Same org scope; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:@opentelemetry/context-zone | AI (dependencies): Official OpenTelemetry package; well-known observability library. | ai | |
| dependencies | unvetted-dep:typesense | AI (dependencies): Known search client library; legitimate dep for a docs portal package. | ai | |
| dependencies | unvetted-dep:@redocly/realm-asyncapi-sdk | AI (dependencies): Same org scope; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:@redocly/portal-plugin-mock-server | AI (dependencies): Same org scope; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:@wojtekmaj/react-datetimerange-picker | AI (dependencies): Known React date picker library; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@redocly/mcp-typescript-sdk | AI (dependencies): Same org scope; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:flexsearch | AI (dependencies): Well-known search library; expected in a docs portal. | ai | |
| dependencies | unvetted-dep:@redocly/theme | AI (dependencies): Same org scope; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:yaml-ast-parser | AI (dependencies): Established YAML parsing library; expected in API docs tooling. | ai | |
| dependencies | unvetted-dep:@redocly/graphql-docs | AI (dependencies): Same org scope; legitimate internal dependency. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.132.1 | 84 / 0 | |
| 0.132.0 | 84 / 0 | |
| 0.131.4 | 85 / 0 | |
| 0.131.3 | 85 / 0 | |
| 0.123.1 | 83 / 0 | |
| 0.123.0 | 83 / 0 | |
| 0.122.2 | 82 / 0 | |
| 0.122.1 | 82 / 0 |
v0.132.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.132.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.131.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.131.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.123.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.123.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.122.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.122.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.