← Home

@redocly/revel-reef

The Revel-Reef package combines Redocly's external developer showcase platform with Redocly's API management platform.

51
Versions
SEE LICENSE IN LICENSE
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

romanhotsiyalawaradamaltmanmarshevskyyvolodymyr-rutskyislavikbezkorovainyi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:enquirer AI (phantom-deps): Bundled dist output obscures imports. ai
provenance publisher-changed-stale AI (provenance): CI publisher change, stable 189d, consistent with legit CI migration. ai
phantom-deps phantom-dep:openapi-sampler AI (phantom-deps): Known OpenAPI tooling dep, bundled build hides import. ai
phantom-deps phantom-dep:@opentelemetry/api AI (phantom-deps): New OTel instrumentation deps used via config, not direct import. ai
source-diff bulk-obfuscated-files:dist AI (source-diff): esbuild-minified dist output, not true obfuscation. ai
phantom-deps phantom-dep:xpath AI (phantom-deps): Minified build output; phantom-dep is a known FP pattern for this package. ai
phantom-deps phantom-dep:events AI (phantom-deps): Config-referenced, benign. ai
phantom-deps phantom-dep:sitemap AI (phantom-deps): Same bundling pattern, stable false positive. ai
phantom-deps phantom-dep:ts-node AI (phantom-deps): Used in build script via loader, not static import. ai
phantom-deps phantom-dep:is-glob AI (phantom-deps): Same bundling pattern, stable false positive. ai
phantom-deps phantom-dep:@redocly/portal-plugin-mock-server AI (phantom-deps): Same org scope, legitimate internal dep. ai
phantom-deps phantom-dep:buffer AI (phantom-deps): Monorepo build package; deps used via bundler/config, not direct import. ai
phantom-deps phantom-dep:fflate AI (phantom-deps): Same as above. ai
phantom-deps phantom-dep:graphql AI (phantom-deps): Same as above. ai
phantom-deps phantom-dep:@redocly/xml-crypto AI (phantom-deps): Same org scope, legitimate internal dep. ai
bogus-package bogus-package AI (bogus-package): Established internal Redocly package, missing metadata is stylistic not spam. ai
source-diff obfuscated-file:dist/constants/l10n/langs/ar.js AI (source-diff): Minified l10n string table, build artifact not obfuscation. ai
source-diff obfuscated-file:dist/server/web-server/routes/catalog/catalog.js AI (source-diff): esbuild-minified first-party source, no malicious behavior. ai
source-diff obfuscated-file:dist/server/web-server/routes/catalog/catalog-relations.js AI (source-diff): esbuild-minified first-party source, no malicious behavior. ai
source-diff obfuscated-file:dist/server/constants/plugins/catalog-entities.js AI (source-diff): esbuild-minified first-party source, no malicious behavior. ai
source-diff obfuscated-file:dist/server/plugins/catalog-entities/database/catalog-entities-service.js AI (source-diff): esbuild-minified first-party source, no malicious behavior. ai
source-diff obfuscated-file:dist/server/plugins/catalog-entities/database/repositories/remote/catalog-entities-remote-repository.js AI (source-diff): esbuild-minified first-party source, no malicious behavior. ai
source-diff obfuscated-file:dist/server/plugins/catalog-entities/database/repositories/local/catalog-entities-local-read-repository.js AI (source-diff): esbuild-minified first-party source, no malicious behavior. ai
source-diff obfuscated-file:dist/server/plugins/catalog-entities/extensions/extractors/api-description/asyncapi-entities-extractor.js AI (source-diff): esbuild-minified first-party source, no malicious behavior. ai
source-diff obfuscated-file:dist/server/plugins/catalog-entities/extensions/extractors/api-description/arazzo-entities-extractor.js AI (source-diff): esbuild-minified first-party source, no malicious behavior. ai
phantom-deps phantom-dep:quickjs-emscripten-core AI (phantom-deps): New dep used indirectly via bundled build; consistent with monorepo pattern. ai
source-diff obfuscated-file:dist/server/plugins/mcp/docs-mcp/tools/graphql/utils.js AI (source-diff): Minified esbuild output from documented build:minify step, not obfuscation. ai
phantom-deps phantom-dep:@hono/zod-validator AI (phantom-deps): New dep used indirectly via bundled build; consistent with monorepo pattern. 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
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/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-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
phantom-deps phantom-dep:ulid 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
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: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

Versions (showing 51 of 51)

Version Deps Published
0.135.0 87 / 0
0.134.0 85 / 0
0.133.1 84 / 0
0.132.1 84 / 0
0.131.3 85 / 0
0.131.0 85 / 0
0.130.1 84 / 0
0.130.0 84 / 0
0.129.1 87 / 0
0.127.0 86 / 0
0.123.0 83 / 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
0.116.0 77 / 0
0.108.5 73 / 0
0.107.3 61 / 0
0.106.1 61 / 0
0.105.0 61 / 0
0.104.0 61 / 0
0.103.0 61 / 0
0.101.0 61 / 0
0.100.3 60 / 0
0.100.2 60 / 0
0.99.2 60 / 0
0.99.1 60 / 0
0.98.0 66 / 0
0.97.6 66 / 0
0.97.5 66 / 0
0.97.3 66 / 0
0.96.0 66 / 0
0.94.0 66 / 0
0.93.2 66 / 0
0.93.1 66 / 0
0.92.6 66 / 0
0.92.5 66 / 0
0.91.5 66 / 0
0.91.3 66 / 0
0.91.2 66 / 0
0.91.1 66 / 0
0.90.0 66 / 0
0.89.3 66 / 0
0.89.2 66 / 0
0.88.3 66 / 0
0.88.2 66 / 0
0.86.2 66 / 0
0.85.1 66 / 0
0.83.0 65 / 0
0.82.1 65 / 0

v0.135.0

2 findings
HIGH New obfuscated file: dist/server/plugins/mcp/docs-mcp/tools/graphql/utils.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.129.1

2 findings
MEDIUM Publisher changed: volodymyr-rutskyi → GitHub Actions (on 2026-01-13, unremoved on npm for 189d) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (volodymyr-rutskyi) on 2026-01-13. It has since remained available on npm for 189 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.127.0

10 findings
HIGH New obfuscated file: dist/constants/l10n/langs/ar.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/server/plugins/catalog-entities/extensions/extractors/api-description/arazzo-entities-extractor.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/server/plugins/catalog-entities/extensions/extractors/api-description/asyncapi-entities-extractor.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/server/plugins/catalog-entities/database/repositories/local/catalog-entities-local-read-repository.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/server/plugins/catalog-entities/database/repositories/remote/catalog-entities-remote-repository.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/server/plugins/catalog-entities/database/catalog-entities-service.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/server/constants/plugins/catalog-entities.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/server/web-server/routes/catalog/catalog-relations.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/server/web-server/routes/catalog/catalog.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.123.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.116.0

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.

v0.108.5

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.

v0.107.3

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.

v0.106.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.

v0.105.0

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.

v0.104.0

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.

v0.103.0

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.

v0.101.0

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.

v0.100.3

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.

v0.100.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.

v0.99.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.

v0.99.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.

v0.98.0

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.

v0.97.6

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.

v0.97.5

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.

v0.97.3

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.

v0.96.0

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.

v0.94.0

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.

v0.93.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.

v0.93.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.

v0.92.6

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.

v0.92.5

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.

v0.91.5

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.

v0.91.3

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.

v0.91.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.

v0.91.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.

v0.90.0

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.

v0.89.3

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.

v0.89.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.

v0.88.3

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.

v0.88.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.

v0.86.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.

v0.85.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.

v0.83.0

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.

v0.82.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.