@pyck/workflow-preview
CLI for previewing and building Pyck workflow UIs. Auto-discovers web components and mobile widgets from a `workflows/` directory, serves them in a dev preview with HMR, and produces Module Federation remotes for production.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:static/mobile/flutter_bootstrap.js | AI (source-diff): Standard Flutter web bootstrap bundle, minified not obfuscated. | ai | |
| source-diff | obfuscated-file:static/mobile/flutter.js | AI (source-diff): Standard Flutter engine JS bundle, minified not obfuscated. | ai | |
| source-diff | obfuscated-file:static/mobile/main.dart.js | AI (source-diff): Dart2JS compiled output, standard Flutter web build artifact. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): CanvasKit wasm binaries are standard Flutter web renderer assets. | ai | |
| phantom-deps | phantom-dep:@pandacss/preset-base | AI (phantom-deps): PandaCSS config reference; stable false positive for this package. | ai | |
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Fires in a test file verifying path traversal is blocked; not credential harvesting. | ai | |
| phantom-deps | phantom-dep:@pandacss/preset-panda | AI (phantom-deps): PandaCSS config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): CSS/config-referenced dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@pandacss/dev | AI (phantom-deps): PandaCSS config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@pyck/panda-preset | AI (phantom-deps): Same-org CSS preset referenced in config; stable false positive. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.2.19 | 11 / 5 | |
| 0.2.18 | 11 / 5 | |
| 0.2.17 | 11 / 5 | |
| 0.2.16 | 11 / 5 | |
| 0.2.15 | 11 / 5 | |
| 0.2.14 | 11 / 5 | |
| 0.2.13 | 11 / 5 | |
| 0.2.12 | 11 / 5 | |
| 0.2.11 | 11 / 5 | |
| 0.2.10 | 11 / 5 | |
| 0.2.9 | 11 / 5 | |
| 0.2.8 | 10 / 5 | |
| 0.2.7 | 10 / 5 | |
| 0.2.6 | 10 / 5 | |
| 0.2.5 | 10 / 5 | |
| 0.2.4 | 9 / 5 | |
| 0.2.3 | 9 / 5 | |
| 0.2.2 | 9 / 5 | |
| 0.2.1 | 9 / 5 | |
| 0.2.0 | 9 / 5 | |
| 0.1.0 | 9 / 5 |
v0.2.18
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.17
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.16
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.15
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.14
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.13
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.12
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.11
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.10
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.9
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.8
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.7
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.6
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.5
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.4
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.3
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.2
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.1
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.2.0
5 findingsPackage contains compiled binaries that could be backdoors: • static/mobile/canvaskit/canvaskit.wasm • static/mobile/canvaskit/chromium/canvaskit.wasm • static/mobile/canvaskit/skwasm_heavy.wasm • static/mobile/canvaskit/skwasm.wasm
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.