@redocly/reef
Reef is Redocly's API management platform that organizes, aids discovery, and monitors APIs throughout their lifecycle.
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/remote-publish-lock-service.js | AI (source-diff): Minified by esbuild-minify-dir build step; content is legitimate domain logic. | ai | |
| source-diff | obfuscated-file:dist/server/plugins/catalog-entities/database/repositories/entities/entities-read-repository.js | AI (source-diff): Minified by esbuild-minify-dir build step; content is legitimate domain logic. | ai | |
| source-diff | obfuscated-file:dist/server/plugins/catalog-entities/database/repositories/entities/entities-write-repository.js | AI (source-diff): Minified by esbuild-minify-dir build step; content is legitimate domain logic. | ai | |
| source-diff | obfuscated-file:dist/server/web-server/routes/mcp-routes/mcp-oauth.js | AI (source-diff): Minified by esbuild-minify-dir build step; content is OAuth flow logic, no exfiltration. | ai | |
| source-diff | obfuscated-file:dist/server/plugins/catalog-entities/database/repositories/relations/relations-read-repository.js | AI (source-diff): Minified by esbuild-minify-dir build step; content is legitimate domain logic. | ai | |
| source-diff | obfuscated-file:dist/server/plugins/catalog-entities/database/catalog-entities-publisher.js | AI (source-diff): Minified by esbuild-minify-dir build step; content is legitimate domain logic. | ai | |
| phantom-deps | phantom-dep:@redocly/portal-plugin-mock-server | AI (phantom-deps): Same org scope; loaded by convention in monorepo, not a direct import. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/context-zone | AI (phantom-deps): Framework-loaded telemetry dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped, loaded by convention per analyzer note. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Listed as peerDependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.134.0 | 85 / 0 | |
| 0.132.1 | 84 / 0 | |
| 0.131.3 | 85 / 0 | |
| 0.128.1 | 86 / 0 | |
| 0.123.0 | 83 / 0 | |
| 0.122.3 | 82 / 0 | |
| 0.122.2 | 82 / 0 | |
| 0.122.1 | 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.128.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.3
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.
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.