@kubb/react-fabric
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/reactPlugin-nOKvfFDq.cjs | AI (source-diff): Readable tsdown/oxc bundle output, not obfuscation; benign build artifact. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-D6399kSr.js | AI (source-diff): Readable bundler ESM output, not obfuscation; benign build artifact. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth from bundling react-reconciler into dist; expected. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-DT9toQPK.js | AI (source-diff): Readable tsdown bundle output; ESM build artifact, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-D4SmGYbm.cjs | AI (source-diff): Readable tsdown bundle output with sourcemaps; minified, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-CpRWhf6R.cjs | AI (source-diff): Bundled tsdown/oxc output, not obfuscation; regenerated each build. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-PG1kqZRe.js | AI (source-diff): Bundled tsdown/oxc output, not obfuscation; regenerated each build. | ai | |
| source-diff | obfuscated-file:dist/Renderer-CgXqdVqV.js | AI (source-diff): Bundled react-reconciler output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/Renderer-CRT9gs-h.cjs | AI (source-diff): Bundled react-reconciler output with intact banners/sourcemaps, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-ixOr00MK.js | AI (source-diff): Readable ESM bundle output, not obfuscation; stable build artifact. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-CXaAO13f.cjs | AI (source-diff): Readable tsdown/rollup bundle output, not obfuscation; stable build artifact. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-DPkN8GTg.cjs | AI (source-diff): Readable tsdown/oxc bundle output, not obfuscation; regenerated per build. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-CNfZ6eQk.js | AI (source-diff): Readable tsdown/oxc bundle output, not obfuscation; regenerated per build. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-CAtVV84d.js | AI (source-diff): tsdown-bundled reconciler output; minified ESM, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-B8F6jVb5.cjs | AI (source-diff): tsdown-bundled reconciler output; readable requires + license banners, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-CsASsju1.js | AI (source-diff): tsdown bundle output, readable named imports/oxc helpers, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-ig-eqmuC.cjs | AI (source-diff): tsdown bundle output, readable named imports/oxc helpers, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-Botk9gkY.cjs | AI (source-diff): tsdown/oxc bundled output, not obfuscation; readable helpers with bundler region markers. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-CjfIGdZW.js | AI (source-diff): tsdown/oxc bundled ESM output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-Ct0yCk0a.cjs | AI (source-diff): Readable tsdown/oxc bundle output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-CjsXM659.js | AI (source-diff): Readable ESM bundle output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-DCT6yE8D.cjs | AI (source-diff): Minified bundle output (tsdown), readable code with normal imports; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-BWBCDdIm.js | AI (source-diff): ESM bundle output; long lines are minification, no malicious behavior. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-BtX7BIDy.js | AI (source-diff): Readable tsdown bundle output, not obfuscation; stable build artifact. | ai | |
| source-diff | obfuscated-file:dist/reactPlugin-B-vyv4g0.cjs | AI (source-diff): Readable tsdown bundle output, not obfuscation; stable build artifact. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 4 / 5 | |
| 0.15.2 | 4 / 5 | |
| 0.15.1 | 4 / 5 | |
| 0.15.0 | 4 / 5 | |
| 0.14.0 | 4 / 5 | |
| 0.13.3 | 4 / 5 | |
| 0.13.2 | 4 / 5 | |
| 0.13.1 | 4 / 5 | |
| 0.13.0 | 4 / 5 | |
| 0.12.11 | 7 / 5 | |
| 0.12.10 | 7 / 5 | |
| 0.12.9 | 7 / 5 | |
| 0.12.8 | 7 / 5 | |
| 0.12.7 | 7 / 5 | |
| 0.12.6 | 7 / 5 | |
| 0.12.5 | 7 / 5 | |
| 0.12.4 | 7 / 5 | |
| 0.12.3 | 7 / 5 | |
| 0.12.2 | 7 / 5 | |
| 0.12.1 | 7 / 5 | |
| 0.12.0 | 6 / 5 | |
| 0.11.8 | 8 / 5 | |
| 0.11.7 | 8 / 5 | |
| 0.11.6 | 8 / 5 | |
| 0.11.5 | 8 / 5 | |
| 0.11.4 | 8 / 5 | |
| 0.11.3 | 8 / 5 | |
| 0.11.2 | 8 / 5 | |
| 0.11.1 | 8 / 5 | |
| 0.11.0 | 8 / 5 | |
| 0.10.0 | 8 / 5 | |
| 0.9.5 | 8 / 5 | |
| 0.9.4 | 8 / 5 | |
| 0.9.3 | 8 / 5 | |
| 0.9.2 | 8 / 5 | |
| 0.9.1 | 8 / 5 | |
| 0.9.0 | 8 / 5 | |
| 0.8.0 | 8 / 5 | |
| 0.7.4 | 8 / 5 | |
| 0.7.3 | 8 / 5 | |
| 0.7.2 | 8 / 5 | |
| 0.7.1 | 8 / 5 | |
| 0.7.0 | 8 / 5 | |
| 0.6.0 | 8 / 5 | |
| 0.5.5 | 8 / 5 | |
| 0.5.4 | 8 / 5 | |
| 0.5.3 | 8 / 5 | |
| 0.5.2 | 8 / 5 | |
| 0.5.1 | 8 / 5 | |
| 0.5.0 | 8 / 5 | |
| 0.4.1 | 8 / 5 | |
| 0.4.0 | 8 / 5 | |
| 0.3.1 | 10 / 3 | |
| 0.3.0 | 10 / 3 | |
| 0.2.19 | 10 / 3 | |
| 0.2.18 | 10 / 3 | |
| 0.2.17 | 10 / 3 | |
| 0.2.16 | 10 / 3 | |
| 0.2.15 | 10 / 3 | |
| 0.2.14 | 10 / 3 | |
| 0.2.13 | 10 / 3 | |
| 0.2.12 | 10 / 3 | |
| 0.2.11 | 10 / 3 | |
| 0.2.10 | 10 / 3 | |
| 0.2.9 | 10 / 3 | |
| 0.2.8 | 10 / 5 | |
| 0.2.7 | 10 / 5 | |
| 0.2.6 | 11 / 4 | |
| 0.2.5 | 10 / 5 | |
| 0.2.4 | 10 / 5 |
v0.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.