@kb-labs/release-manager-cli
KB Labs Release Manager - CLI commands for release management
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/widgets/__federation_expose_ReleasePage.js | AI (source-diff): Standard rspack Module Federation bundle; samples show React/UI library code. | ai | |
| source-diff | obfuscated-file:dist/widgets/117.js | AI (source-diff): Rspack bundle chunk containing ant-design UI component exports; legitimate minified output. | ai | |
| source-diff | obfuscated-file:dist/widgets/165.js | AI (source-diff): Rspack bundle chunk containing minified react-dom; legitimate build output. | ai | |
| source-diff | obfuscated-file:dist/widgets/370.js | AI (source-diff): Rspack bundle chunk with React hooks/context; legitimate minified output. | ai | |
| source-diff | obfuscated-file:dist/widgets/405.js | AI (source-diff): Rspack bundle chunk with React core symbols; legitimate minified output. | ai | |
| source-diff | obfuscated-file:dist/widgets/418.js | AI (source-diff): Rspack bundle chunk with chart/math libraries; legitimate minified output. | ai | |
| source-diff | net-exec-file:dist/widgets/418.js | AI (source-diff): Network calls in this chunk are chart/data-fetching library code, not dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/widgets/451.js | AI (source-diff): Rspack bundle chunk containing dayjs library; legitimate minified output. | ai | |
| source-diff | obfuscated-file:dist/widgets/546.js | AI (source-diff): Rspack bundle chunk; legitimate minified output consistent with build pipeline. | ai | |
| source-diff | obfuscated-file:dist/widgets/694.js | AI (source-diff): Rspack bundle chunk; legitimate minified output consistent with build pipeline. | ai | |
| source-diff | obfuscated-file:dist/widgets/775.js | AI (source-diff): Rspack bundle chunk; legitimate minified output consistent with build pipeline. | ai | |
| source-diff | obfuscated-file:dist/widgets/805.js | AI (source-diff): Rspack bundle chunk; legitimate minified output consistent with build pipeline. | ai | |
| source-diff | net-exec-file:dist/widgets/805.js | AI (source-diff): Network calls in this chunk are consistent with UI/data library code, not dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/widgets/919.js | AI (source-diff): Rspack bundle chunk; legitimate minified output consistent with build pipeline. | ai | |
| source-diff | obfuscated-file:dist/widgets/968.js | AI (source-diff): Rspack bundle chunk; legitimate minified output consistent with build pipeline. | ai | |
| source-diff | obfuscated-file:dist/widgets/remoteEntry.js | AI (source-diff): Module Federation remoteEntry is standard rspack output; legitimate minified bundle. | ai | |
| source-diff | net-exec-file:dist/widgets/remoteEntry.js | AI (source-diff): Module Federation remote entry uses dynamic loading by design; not dropper behavior. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by addition of rspack Module Federation widget bundle (build:studio script). | ai | |
| phantom-deps | phantom-dep:@kb-labs/studio-plugin-tools | AI (phantom-deps): Same org scope; likely consumed transitively or via Module Federation at runtime. | ai | |
| phantom-deps | phantom-dep:@kb-labs/release-manager-checks | AI (phantom-deps): Same org scope; likely consumed transitively or via Module Federation at runtime. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 2.94.0 | 10 / 14 | |
| 2.93.0 | 10 / 14 | |
| 2.89.0 | 10 / 14 | |
| 2.88.0 | 10 / 14 | |
| 2.87.0 | 10 / 14 | |
| 2.82.0 | 10 / 14 | |
| 2.81.0 | 10 / 14 | |
| 2.80.0 | 10 / 14 | |
| 2.79.0 | 10 / 14 | |
| 2.77.0 | 10 / 14 | |
| 2.75.0 | 10 / 14 | |
| 2.74.0 | 10 / 14 | |
| 2.73.0 | 10 / 14 | |
| 2.72.0 | 10 / 14 | |
| 2.68.0 | 10 / 14 | |
| 2.67.0 | 10 / 14 | |
| 2.66.0 | 10 / 14 | |
| 2.65.0 | 10 / 14 | |
| 2.64.0 | 10 / 14 | |
| 2.62.0 | 10 / 14 | |
| 2.61.0 | 10 / 14 | |
| 2.60.0 | 10 / 14 | |
| 2.59.0 | 10 / 14 | |
| 2.58.0 | 10 / 14 | |
| 2.57.0 | 10 / 14 | |
| 2.56.0 | 10 / 14 | |
| 2.55.0 | 10 / 14 | |
| 2.54.0 | 10 / 14 | |
| 2.53.0 | 10 / 14 | |
| 2.47.0 | 10 / 14 | |
| 2.46.0 | 10 / 14 | |
| 2.45.0 | 10 / 14 | |
| 2.44.0 | 10 / 14 | |
| 2.43.0 | 10 / 14 | |
| 2.42.0 | 10 / 14 | |
| 2.41.0 | 10 / 14 | |
| 2.40.0 | 10 / 14 | |
| 2.39.0 | 10 / 14 | |
| 2.38.0 | 10 / 14 | |
| 2.37.0 | 10 / 14 | |
| 2.36.0 | 10 / 14 | |
| 2.35.0 | 10 / 14 | |
| 2.34.0 | 10 / 14 | |
| 2.33.0 | 10 / 14 | |
| 2.32.0 | 10 / 14 | |
| 2.31.0 | 10 / 14 | |
| 2.30.0 | 10 / 14 | |
| 2.29.0 | 10 / 14 | |
| 2.28.0 | 10 / 14 | |
| 2.25.0 | 10 / 14 | |
| 2.23.0 | 10 / 14 | |
| 2.22.0 | 10 / 14 | |
| 2.20.0 | 10 / 14 | |
| 2.19.0 | 10 / 14 | |
| 2.18.0 | 10 / 14 | |
| 2.17.0 | 10 / 14 | |
| 2.15.0 | 10 / 14 | |
| 2.14.0 | 10 / 14 | |
| 2.13.0 | 10 / 14 | |
| 2.12.0 | 10 / 14 | |
| 2.11.0 | 10 / 14 | |
| 2.10.0 | 10 / 14 | |
| 2.9.0 | 10 / 14 | |
| 2.7.0 | 10 / 14 | |
| 2.6.0 | 10 / 14 | |
| 0.6.0 | 10 / 14 | |
| 0.5.0 | 10 / 14 |
v2.94.0
18 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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.93.0
18 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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.