@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Monorepo build likely resolves deps via dist bundling, not static import. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Same pattern as other phantom deps in this build. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Redocly package, established publisher; missing metadata is cosmetic. | ai | |
| source-diff | obfuscated-file:dist/constants/l10n/langs/ar.js | AI (source-diff): i18n JSON data bundled into single line, not code obfuscation. | ai | |
| phantom-deps | phantom-dep:anser | AI (phantom-deps): Large monorepo package; config-referenced deps are expected false positives. | ai | |
| source-diff | obfuscated-file:dist/server/plugins/catalog-entities/extensions/extractors/api-description/arazzo-entities-extractor.js | AI (source-diff): esbuild-minified build output per package's own build:minify script. | ai | |
| dependencies | unvetted-dep:@redocly/mcp-typescript-sdk | AI (dependencies): Same-org first-party package. | ai | |
| phantom-deps | phantom-dep:ulid | AI (phantom-deps): Large monorepo package.json; config-referenced not unused. | ai | |
| source-diff | obfuscated-file:dist/server/plugins/mcp/docs-mcp/tools/graphql/utils.js | AI (source-diff): Minified build output from documented esbuild-minify step, not true obfuscation. | ai | |
| 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/catalog-entities-publisher.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 | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Listed as peerDependency; phantom-dep heuristic 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:@opentelemetry/context-zone | AI (phantom-deps): Framework-loaded telemetry dep; stable false positive for this package. | 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 |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.135.0 | 87 / 0 | |
| 0.134.0 | 85 / 0 | |
| 0.132.1 | 84 / 0 | |
| 0.131.3 | 85 / 0 | |
| 0.131.0 | 85 / 0 | |
| 0.129.0 | 87 / 0 | |
| 0.128.1 | 86 / 0 | |
| 0.127.0 | 86 / 0 | |
| 0.123.0 | 83 / 0 | |
| 0.122.3 | 82 / 0 | |
| 0.122.2 | 82 / 0 | |
| 0.122.1 | 82 / 0 | |
| 0.122.0 | 82 / 0 | |
| 0.121.1 | 80 / 0 | |
| 0.121.0 | 80 / 0 | |
| 0.99.2 | 60 / 0 | |
| 0.98.2 | 66 / 0 | |
| 0.98.1 | 66 / 0 | |
| 0.98.0 | 66 / 0 | |
| 0.97.4 | 66 / 0 | |
| 0.97.3 | 66 / 0 | |
| 0.97.0 | 66 / 0 | |
| 0.94.2 | 66 / 0 | |
| 0.93.2 | 66 / 0 | |
| 0.92.4 | 66 / 0 | |
| 0.91.2 | 66 / 0 | |
| 0.91.1 | 66 / 0 | |
| 0.89.5 | 66 / 0 | |
| 0.89.3 | 66 / 0 | |
| 0.89.0 | 66 / 0 | |
| 0.86.4 | 66 / 0 | |
| 0.86.0 | 66 / 0 |
v0.135.0
2 findingsNewly 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.131.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.127.0
8 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.
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.99.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.94.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.93.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.92.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.91.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.91.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.89.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.89.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.86.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.86.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.