@gbasin/agentboard
Web GUI for tmux optimized for AI agent TUIs
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@xterm/addon-web-links | AI (phantom-deps): Bundled CLI ships prebuilt binaries; deps referenced in config/build but not directly imported is expected. | ai | |
| phantom-deps | phantom-dep:@untitledui-icons/react | AI (phantom-deps): Same bundled-binary pattern; phantom-dep is a build artifact, not a real import gap. | ai | |
| phantom-deps | phantom-dep:@base-ui-components/react | AI (phantom-deps): Same bundled-binary pattern; phantom-dep is a build artifact, not a real import gap. | ai | |
| phantom-deps | phantom-dep:@fontsource-variable/jetbrains-mono | AI (phantom-deps): Same bundled-binary pattern; font dep referenced in build config only. | ai | |
| phantom-deps | phantom-dep:motion | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:zustand | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:node-pty | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:@xterm/xterm | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/core | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:@base-ui/react | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Bundled CLI; deps compiled into artifact, not directly imported in source visible to analyzer. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/sortable | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/utilities | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:@xterm/addon-webgl | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:@xterm/addon-search | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:@xterm/addon-progress | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:@xterm/addon-clipboard | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:@xterm/addon-serialize | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:@xterm/addon-fit | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Bundled CLI; same pattern. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): Bundled CLI; same pattern. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.2.49 | 23 / 17 | |
| 0.2.48 | 23 / 17 | |
| 0.2.47 | 23 / 17 | |
| 0.2.46 | 23 / 17 | |
| 0.2.45 | 23 / 17 | |
| 0.2.44 | 23 / 17 | |
| 0.2.43 | 23 / 17 | |
| 0.2.42 | 23 / 17 | |
| 0.2.41 | 23 / 17 | |
| 0.2.40 | 23 / 17 | |
| 0.2.39 | 23 / 17 | |
| 0.2.38 | 23 / 17 | |
| 0.2.37 | 23 / 17 | |
| 0.2.36 | 23 / 17 | |
| 0.2.35 | 23 / 17 | |
| 0.2.34 | 23 / 17 | |
| 0.2.33 | 23 / 17 | |
| 0.2.32 | 23 / 17 | |
| 0.2.31 | 23 / 17 | |
| 0.2.30 | 23 / 17 | |
| 0.2.29 | 23 / 17 | |
| 0.2.28 | 23 / 17 | |
| 0.2.27 | 23 / 17 | |
| 0.2.26 | 23 / 17 | |
| 0.2.25 | 23 / 17 | |
| 0.2.24 | 23 / 17 | |
| 0.2.23 | 23 / 17 | |
| 0.2.22 | 23 / 17 | |
| 0.2.21 | 23 / 17 | |
| 0.2.20 | 23 / 17 | |
| 0.2.19 | 23 / 17 | |
| 0.2.18 | 23 / 17 | |
| 0.2.17 | 23 / 17 | |
| 0.2.16 | 23 / 17 | |
| 0.2.15 | 23 / 17 | |
| 0.2.14 | 23 / 17 | |
| 0.2.13 | 23 / 16 | |
| 0.2.12 | 23 / 16 | |
| 0.2.11 | 23 / 16 | |
| 0.2.9 | 23 / 16 | |
| 0.2.8 | 23 / 16 | |
| 0.2.7 | 23 / 16 | |
| 0.2.5 | 23 / 16 | |
| 0.1.8 | 23 / 16 | |
| 0.1.7 | 23 / 16 | |
| 0.1.3 | 23 / 16 | |
| 0.1.0 | 23 / 16 |
v0.2.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.