@flows/react
Flows React SDK – Build native product growth experiences, your way
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/debug-panel-KPDSFK7D.mjs | AI (source-diff): Standard tsup minified bundle output; content is readable CSS/React code, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-FFUUHWCD.mjs | AI (source-diff): Standard minified build output (CSS vars + React hooks); not obfuscated malware. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-QZYKYQWA.mjs | AI (source-diff): Same pattern as sibling file — minified build artifact, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-QOWICDUM.mjs | AI (source-diff): Standard tsup minified bundle output; CSS variables and React imports are clearly visible, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-KQMCGKT4.mjs | AI (source-diff): Minified build artifact from tsup; sample shows normal CSS/React code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-2G7ZCIVE.mjs | AI (source-diff): Minified bundler output (tsup); readable CSS and React imports confirm legitimate build artifact. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-LS7XCTW6.mjs | AI (source-diff): Minified build artifact from tsup/esbuild; sample shows normal CSS and React imports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-7NFMXKUQ.mjs | AI (source-diff): Minified build artifact from tsup; sample shows normal React/CSS code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-TEWYFIFS.mjs | AI (source-diff): Minified bundler output (tsup); content is readable CSS/React code, not obfuscated malware. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): clsx is a well-established, widely-trusted utility; no malware risk. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-72L5HT6X.mjs | AI (source-diff): Minified build artifact from tsup; content is readable CSS/React code, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-TTBRISEC.mjs | AI (source-diff): Standard tsup bundle output; sample shows CSS vars and React imports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-6DVLNT5L.mjs | AI (source-diff): Standard tsup minified ESM output; same pattern as sibling chunk, legitimate build artifact. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-4HIQRHPU.mjs | AI (source-diff): Standard tsup minified ESM output; readable CSS and React imports confirm legitimate build artifact. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-XO4F23R2.mjs | AI (source-diff): Long lines are inlined CSS strings in a tsup bundle; readable code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-YY3YAZ5C.mjs | AI (source-diff): Minified tsup build output; content is readable CSS/React code, not obfuscated malware. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher with SLSA provenance is a legitimate CI/CD automation pattern. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-C5EHEV3Z.mjs | AI (source-diff): Minified tsup build output; content is readable CSS/React code, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-GGNFWKGX.mjs | AI (source-diff): Same pattern as sibling file; minified build artifact from tsup, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-555ZWVH2.mjs | AI (source-diff): Standard tsup-minified React component output; long lines are bundled CSS-in-JS, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-NUZJSCNE.mjs | AI (source-diff): Minified tsup build output; content is a readable React debug panel component, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-N23VIMIT.mjs | AI (source-diff): Minified bundler output (tsup); content is readable CSS/React code, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/debug-panel-SF4TWNRX.mjs | AI (source-diff): Minified tsup bundle output; sample shows plain CSS and React imports, not malicious obfuscation. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 1.24.0 | 2 / 10 | |
| 1.23.0 | 2 / 10 | |
| 1.22.3 | 2 / 10 | |
| 1.22.2 | 2 / 10 | |
| 1.22.1 | 2 / 10 | |
| 1.22.0 | 2 / 10 | |
| 1.21.0 | 2 / 10 | |
| 1.20.1 | 2 / 10 | |
| 1.20.0 | 2 / 10 | |
| 1.19.3 | 2 / 10 | |
| 1.19.2 | 2 / 10 | |
| 1.19.1 | 2 / 10 | |
| 1.19.0 | 2 / 10 | |
| 1.18.2 | 2 / 10 | |
| 1.18.1 | 2 / 10 | |
| 1.18.0 | 2 / 10 | |
| 1.17.2 | 2 / 10 | |
| 1.17.1 | 2 / 10 | |
| 1.17.0 | 2 / 10 | |
| 1.16.2 | 2 / 10 | |
| 1.16.1 | 2 / 10 | |
| 1.16.0 | 2 / 10 | |
| 1.15.1 | 2 / 10 | |
| 1.15.0 | 2 / 10 | |
| 1.14.0 | 1 / 9 | |
| 1.13.0 | 0 / 9 | |
| 1.12.0 | 0 / 9 | |
| 1.11.0 | 0 / 9 | |
| 1.10.3 | 0 / 9 | |
| 1.10.2 | 0 / 9 | |
| 1.10.1 | 0 / 9 | |
| 1.10.0 | 0 / 9 | |
| 1.9.1 | 0 / 9 |
v1.24.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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.23.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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.0
4 findingsThis version was published by a different npm account than previous versions on 2026-02-27. This could indicate a legitimate maintainer transition or an account compromise.
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.20.1
4 findingsThis version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.20.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.
v1.19.3
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.
v1.19.2
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.
v1.19.1
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.
v1.19.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.
v1.18.2
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.
v1.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.1
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.
v1.17.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.
v1.16.2
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.
v1.16.1
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.
v1.16.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.
v1.15.1
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.
v1.15.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.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.