@fabriccode/kanban — Greenflagged

A kanban foundation for coding agents — Fabric edition

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

preddy4690

Keywords

kanbanagentsclitask-managementtypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@clinebot/shared	AI (phantom-deps): First-party org dep; bundled CLI pattern; stable FP.	ai	2026/05/30
source-diff	obfuscated-file:dist/web-ui/assets/index-D-yWejxo.js	AI (source-diff): Standard Vite-bundled web UI output with accompanying source map; not malicious obfuscation.	ai	2026/05/29
source-diff	obfuscated-file:dist/web-ui/assets/index-DTsMNw46.js	AI (source-diff): Standard Vite-bundled web UI output with accompanying source map; not malicious obfuscation.	ai	2026/05/27
source-diff	encoded-string-file:dist/cli-main.js	AI (source-diff): Long base64 string is the llhttp WASM binary from undici — a well-known legitimate pattern.	ai	2026/05/27
phantom-deps	phantom-dep:@xterm/headless	AI (phantom-deps): Bundled CLI; deps used in dist bundle, not directly imported in source.	ai	2026/05/15
phantom-deps	phantom-dep:ora	AI (phantom-deps): Bundled CLI; deps used in dist bundle, not directly imported in source.	ai	2026/05/15
phantom-deps	phantom-dep:@xterm/addon-serialize	AI (phantom-deps): Bundled CLI; deps used in dist bundle, not directly imported in source.	ai	2026/05/15
phantom-deps	phantom-dep:@trpc/server	AI (phantom-deps): CLI/bundled package; deps used in build or sub-packages, not direct imports.	ai	2026/05/15
phantom-deps	phantom-dep:@clinebot/core	AI (phantom-deps): CLI/bundled package; deps used in build or sub-packages, not direct imports.	ai	2026/05/15
phantom-deps	phantom-dep:proper-lockfile	AI (phantom-deps): CLI/bundled package; deps used in build or sub-packages, not direct imports.	ai	2026/05/15
phantom-deps	phantom-dep:@clinebot/agents	AI (phantom-deps): CLI/bundled package; deps used in build or sub-packages, not direct imports.	ai	2026/05/15
phantom-deps	phantom-dep:@modelcontextprotocol/sdk	AI (phantom-deps): CLI/bundled package; deps used in build or sub-packages, not direct imports.	ai	2026/05/15
phantom-deps	phantom-dep:@clinebot/llms	AI (phantom-deps): CLI/bundled package; deps used in build or sub-packages, not direct imports.	ai	2026/05/15
phantom-deps	phantom-dep:ws	AI (phantom-deps): CLI/bundled package; deps used in build or sub-packages, not direct imports.	ai	2026/05/15
phantom-deps	phantom-dep:open	AI (phantom-deps): CLI/bundled package; deps used in build or sub-packages, not direct imports.	ai	2026/05/15
phantom-deps	phantom-dep:commander	AI (phantom-deps): CLI/bundled package; deps used in build or sub-packages, not direct imports.	ai	2026/05/15
phantom-deps	phantom-dep:tree-kill	AI (phantom-deps): CLI/bundled package; deps used in build or sub-packages, not direct imports.	ai	2026/05/15
phantom-deps	phantom-dep:@sentry/node	AI (phantom-deps): CLI/bundled package; deps used in build or sub-packages, not direct imports.	ai	2026/05/15
phantom-deps	phantom-dep:@trpc/client	AI (phantom-deps): CLI/bundled package; deps used in build or sub-packages, not direct imports.	ai	2026/05/15
phantom-deps	phantom-dep:node-pty	AI (phantom-deps): node-pty is a native terminal binding; CLI tools commonly use it indirectly via config/runtime paths.	ai	2026/04/29
phantom-deps	phantom-dep:systray2	AI (phantom-deps): systray2 is a platform-specific optional dep; phantom-dep false positive for conditional usage.	ai	2026/04/29

Versions (showing 38 of 38)

Version	Deps	Published
0.3.24	2 / 26	2026-05-15
0.3.21	2 / 26	2026-05-02
0.3.18	2 / 26	2026-04-26
0.3.13	12 / 18	2026-04-22
0.3.12	12 / 18	2026-04-22
0.3.11	12 / 18	2026-04-21
0.3.10	12 / 18	2026-04-20
0.3.9	12 / 18	2026-04-20
0.3.7	12 / 18	2026-04-16
0.3.5	12 / 18	2026-04-16
0.3.3	12 / 18	2026-04-16
0.3.1	12 / 18	2026-04-15
0.3.0	12 / 18	2026-04-14
0.2.18	12 / 18	2026-04-14
0.2.17	11 / 18	2026-04-12
0.2.16	11 / 18	2026-04-11
0.2.15	18 / 11	2026-04-10
0.2.10	18 / 11	2026-04-09
0.2.8	18 / 11	2026-04-08
0.2.7	18 / 11	2026-04-07
0.2.1	18 / 11	2026-04-02
0.1.86	17 / 11	2026-03-30
0.1.85	17 / 11	2026-03-30
0.1.83	17 / 11	2026-03-30
0.1.82	17 / 11	2026-03-29
0.1.79	17 / 11	2026-03-29
0.1.77	17 / 11	2026-03-29
0.1.76	17 / 11	2026-03-29
0.1.73	17 / 11	2026-03-29
0.1.65	17 / 11	2026-03-29
0.1.64	17 / 11	2026-03-29
0.1.61	17 / 11	2026-03-29
0.1.56	14 / 11	2026-03-29
0.1.55	14 / 11	2026-03-29
0.1.54	14 / 11	2026-03-29
0.1.53	14 / 11	2026-03-29
0.1.52	14 / 11	2026-03-29
0.1.51	14 / 11	2026-03-29

v0.3.24

3 findings

HIGH New obfuscated file: dist/web-ui/assets/index-D-yWejxo.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 Long encoded string in modified file: dist/cli-main.js source-diff

Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.3.21

3 findings

HIGH New obfuscated file: dist/web-ui/assets/index-DTsMNw46.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 Long encoded string in modified file: dist/cli-main.js source-diff

Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.3.18

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.3.13

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.3.12

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.3.11

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.3.10

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.3.9

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.3.7

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.3.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.3.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.3.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.3.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.2.18

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.2.17

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.2.16

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.2.15

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.2.10

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.2.8

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.2.7

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.2.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.1.86

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.1.85

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.1.83

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.1.82

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.1.79

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.1.77

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.1.76

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.1.73

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.1.65

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.1.64

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.1.61

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.1.56

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.1.55

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.1.54

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.1.53

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.1.52

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.1.51

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.