@redocly/revel-reef
The Revel-Reef package combines Redocly's external developer showcase platform with Redocly's API management platform.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/server/plugins/catalog-entities/database/catalog-entities-publisher.js | AI (source-diff): esbuild minified output per declared build:minify script; readable business logic, no malicious indicators. | ai | |
| source-diff | obfuscated-file:dist/server/plugins/catalog-entities/database/repositories/entities/entities-read-repository.js | AI (source-diff): esbuild minified output; readable ORM query logic, consistent with package purpose. | ai | |
| source-diff | obfuscated-file:dist/server/plugins/catalog-entities/database/repositories/entities/entities-write-repository.js | AI (source-diff): esbuild minified output; readable write-repository logic, no malicious indicators. | ai | |
| source-diff | obfuscated-file:dist/server/web-server/routes/mcp-routes/mcp-oauth.js | AI (source-diff): esbuild minified output; MCP OAuth flow using standard node:crypto and JWT, consistent with declared MCP SDK dependency. | ai | |
| source-diff | obfuscated-file:dist/server/plugins/catalog-entities/database/repositories/relations/relations-read-repository.js | AI (source-diff): esbuild minified output; readable drizzle-orm query logic. | ai | |
| source-diff | obfuscated-file:dist/server/plugins/catalog-entities/database/remote-publish-lock-service.js | AI (source-diff): esbuild minified output; lock-service logic with no exfiltration indicators. | ai | |
| phantom-deps | phantom-dep:ulid | AI (phantom-deps): Large monorepo bundle; phantom-dep heuristic unreliable for this package. | ai | |
| phantom-deps | phantom-dep:anser | AI (phantom-deps): Large monorepo bundle; phantom-dep heuristic unreliable for this package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Large monorepo bundle; phantom-dep heuristic unreliable for this package. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Large monorepo bundle; phantom-dep heuristic unreliable for this package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Large monorepo bundle; phantom-dep heuristic unreliable for this package. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Declared as peerDependency; phantom-dep false positive. | ai | |
| phantom-deps | phantom-dep:@emotion/is-prop-valid | AI (phantom-deps): Newly added runtime dep; phantom-dep heuristic unreliable for bundled packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.134.0 | 85 / 0 | |
| 0.132.1 | 84 / 0 | |
| 0.131.3 | 85 / 0 | |
| 0.131.0 | 85 / 0 | |
| 0.122.3 | 82 / 0 | |
| 0.122.1 | 82 / 0 | |
| 0.122.0 | 82 / 0 | |
| 0.121.1 | 80 / 0 | |
| 0.121.0 | 80 / 0 |
v0.134.0
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.131.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.131.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.122.3
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.
v0.122.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.121.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.121.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.