@agentuity/workbench
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Missing metadata is a stable characteristic of this org's workbench package, not a spam/malware indicator. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org package with active maintainer rotation; publisher-changed-known-maintainer INFO confirms huijiro is a legitimate maintainer. | ai | |
| source-diff | obfuscated-file:dist/components/ai-elements/open-in-chat.js | AI (source-diff): Long lines are inlined SVG path data in compiled TSX output, not obfuscation. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-avatar | AI (dependencies): Well-known Radix UI component library; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:bun-plugin-tailwind | AI (dependencies): Build-time Tailwind plugin; referenced in build scripts, not a runtime risk. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-hover-card | AI (dependencies): Well-known Radix UI component library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xyflow/react | AI (phantom-deps): Config-level usage in UI workbench. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): Config-level usage in UI workbench. | ai | |
| phantom-deps | phantom-dep:non.geist | AI (phantom-deps): Font package referenced in CSS/config, not imported in JS. | ai | |
| phantom-deps | phantom-dep:@agentuity/react | AI (phantom-deps): Same-org dep; expected in workbench package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Config/type-level usage in a UI workbench; not a direct import pattern. | ai | |
| phantom-deps | phantom-dep:@hookform/resolvers | AI (phantom-deps): Config-level usage in UI workbench. | ai | |
| phantom-deps | phantom-dep:bun-plugin-tailwind | AI (phantom-deps): Build tool referenced in bun config, not direct JS import. | ai | |
| phantom-deps | phantom-dep:tailwindcss-animate | AI (phantom-deps): CSS plugin referenced in tailwind config, not direct JS import. | ai | |
| phantom-deps | phantom-dep:embla-carousel-react | AI (phantom-deps): Config-level usage in UI workbench. | ai | |
| phantom-deps | phantom-dep:tokenlens | AI (phantom-deps): Utility referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:streamdown | AI (phantom-deps): Referenced in config files, consistent with workbench pattern. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/react | AI (phantom-deps): Peer/config-level usage in UI workbench. | ai |
Versions (showing 100 of 184)
| Version | Deps | Published |
|---|---|---|
| 2.0.29 | 28 / 12 | |
| 2.0.28 | 28 / 12 | |
| 2.0.27 | 28 / 12 | |
| 2.0.26 | 28 / 12 | |
| 2.0.25 | 28 / 12 | |
| 2.0.24 | 28 / 12 | |
| 2.0.23 | 28 / 12 | |
| 2.0.22 | 28 / 12 | |
| 2.0.21 | 28 / 12 | |
| 2.0.20 | 28 / 12 | |
| 2.0.19 | 28 / 12 | |
| 2.0.18 | 28 / 12 | |
| 2.0.17 | 28 / 12 | |
| 2.0.16 | 28 / 12 | |
| 2.0.15 | 28 / 12 | |
| 2.0.14 | 28 / 12 | |
| 2.0.13 | 28 / 12 | |
| 2.0.12 | 28 / 12 | |
| 2.0.11 | 28 / 12 | |
| 2.0.10 | 28 / 12 | |
| 2.0.9 | 28 / 12 | |
| 2.0.8 | 28 / 12 | |
| 2.0.7 | 28 / 12 | |
| 2.0.6 | 28 / 12 | |
| 2.0.5 | 28 / 12 | |
| 2.0.4 | 28 / 12 | |
| 2.0.3 | 28 / 12 | |
| 2.0.2 | 28 / 12 | |
| 2.0.1 | 28 / 12 | |
| 2.0.0 | 28 / 12 | |
| 1.0.64 | 28 / 12 | |
| 1.0.63 | 28 / 12 | |
| 1.0.62 | 28 / 12 | |
| 1.0.61 | 28 / 12 | |
| 1.0.60 | 28 / 12 | |
| 1.0.59 | 28 / 12 | |
| 1.0.58 | 28 / 12 | |
| 1.0.57 | 28 / 12 | |
| 1.0.56 | 28 / 12 | |
| 1.0.55 | 28 / 12 | |
| 1.0.54 | 28 / 12 | |
| 1.0.53 | 28 / 12 | |
| 1.0.52 | 28 / 12 | |
| 1.0.51 | 28 / 12 | |
| 1.0.50 | 28 / 12 | |
| 1.0.49 | 28 / 12 | |
| 1.0.48 | 28 / 12 | |
| 1.0.47 | 28 / 12 | |
| 1.0.46 | 28 / 12 | |
| 1.0.45 | 28 / 12 | |
| 1.0.44 | 28 / 12 | |
| 1.0.43 | 28 / 12 | |
| 1.0.42 | 28 / 12 | |
| 1.0.41 | 28 / 12 | |
| 1.0.40 | 28 / 12 | |
| 1.0.39 | 28 / 12 | |
| 1.0.38 | 28 / 12 | |
| 1.0.37 | 28 / 12 | |
| 1.0.36 | 28 / 12 | |
| 1.0.35 | 28 / 12 | |
| 1.0.34 | 28 / 12 | |
| 1.0.33 | 28 / 12 | |
| 1.0.32 | 28 / 12 | |
| 1.0.31 | 28 / 12 | |
| 1.0.30 | 28 / 12 | |
| 1.0.29 | 28 / 12 | |
| 1.0.28 | 28 / 12 | |
| 1.0.27 | 28 / 12 | |
| 1.0.26 | 28 / 12 | |
| 1.0.25 | 28 / 12 | |
| 1.0.24 | 28 / 12 | |
| 1.0.23 | 28 / 12 | |
| 1.0.22 | 28 / 12 | |
| 1.0.21 | 28 / 12 | |
| 1.0.20 | 28 / 12 | |
| 1.0.19 | 28 / 12 | |
| 1.0.18 | 28 / 12 | |
| 1.0.17 | 28 / 12 | |
| 1.0.16 | 28 / 12 | |
| 1.0.15 | 28 / 12 | |
| 1.0.14 | 28 / 12 | |
| 1.0.13 | 28 / 12 | |
| 1.0.12 | 28 / 12 | |
| 1.0.11 | 28 / 12 | |
| 1.0.10 | 28 / 12 | |
| 1.0.9 | 28 / 12 | |
| 1.0.8 | 28 / 12 | |
| 1.0.7 | 28 / 12 | |
| 1.0.5 | 28 / 12 | |
| 1.0.4 | 28 / 12 | |
| 1.0.3 | 28 / 12 | |
| 1.0.2 | 28 / 12 | |
| 1.0.1 | 28 / 12 | |
| 1.0.0 | 28 / 12 | |
| 0.1.45 | 28 / 12 | |
| 0.1.44 | 28 / 12 | |
| 0.1.43 | 28 / 12 | |
| 0.1.42 | 28 / 12 | |
| 0.1.41 | 28 / 12 | |
| 0.1.40 | 28 / 12 |
v2.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (p0tofpie) than the most recent previously approved version (huijiro) on 2026-06-10, but p0tofpie is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.22
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (p0tofpie) than the most recent previously approved version (jhaynie) on 2026-05-27, but p0tofpie is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jhaynie) than the most recent previously approved version (p0tofpie) on 2026-04-28, but jhaynie is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (p0tofpie) than the most recent previously approved version (jhaynie) on 2026-04-03, but p0tofpie is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jhaynie) than the most recent previously approved version (p0tofpie) on 2026-03-27, but jhaynie is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jhaynie) than the most recent previously approved version (p0tofpie) on 2026-03-20, but jhaynie is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.