@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 84 of 184)
| Version | Deps | Published |
|---|---|---|
| 0.1.39 | 28 / 12 | |
| 0.1.38 | 28 / 12 | |
| 0.1.37 | 28 / 12 | |
| 0.1.36 | 28 / 12 | |
| 0.1.35 | 28 / 12 | |
| 0.1.34 | 28 / 12 | |
| 0.1.33 | 28 / 12 | |
| 0.1.32 | 28 / 12 | |
| 0.1.31 | 28 / 12 | |
| 0.1.30 | 28 / 12 | |
| 0.1.29 | 28 / 12 | |
| 0.1.28 | 28 / 12 | |
| 0.1.27 | 28 / 12 | |
| 0.1.26 | 28 / 12 | |
| 0.1.25 | 28 / 12 | |
| 0.1.24 | 28 / 12 | |
| 0.1.23 | 28 / 12 | |
| 0.1.22 | 28 / 12 | |
| 0.1.21 | 28 / 12 | |
| 0.1.20 | 28 / 12 | |
| 0.1.19 | 28 / 12 | |
| 0.1.18 | 28 / 12 | |
| 0.1.17 | 28 / 12 | |
| 0.1.16 | 28 / 12 | |
| 0.1.15 | 28 / 12 | |
| 0.1.14 | 28 / 12 | |
| 0.1.13 | 28 / 12 | |
| 0.1.12 | 28 / 12 | |
| 0.1.11 | 28 / 12 | |
| 0.1.10 | 28 / 12 | |
| 0.1.9 | 28 / 12 | |
| 0.1.8 | 28 / 12 | |
| 0.1.7 | 28 / 12 | |
| 0.1.6 | 28 / 12 | |
| 0.1.5 | 28 / 12 | |
| 0.1.4 | 28 / 12 | |
| 0.1.3 | 28 / 12 | |
| 0.1.2 | 28 / 12 | |
| 0.1.1 | 28 / 12 | |
| 0.1.0 | 28 / 12 | |
| 0.0.112 | 28 / 12 | |
| 0.0.111 | 28 / 12 | |
| 0.0.110 | 28 / 12 | |
| 0.0.109 | 28 / 12 | |
| 0.0.108 | 28 / 12 | |
| 0.0.107 | 28 / 12 | |
| 0.0.106 | 28 / 12 | |
| 0.0.105 | 28 / 12 | |
| 0.0.104 | 28 / 12 | |
| 0.0.103 | 28 / 9 | |
| 0.0.102 | 28 / 9 | |
| 0.0.101 | 28 / 9 | |
| 0.0.100 | 28 / 8 | |
| 0.0.99 | 28 / 8 | |
| 0.0.98 | 28 / 8 | |
| 0.0.97 | 28 / 8 | |
| 0.0.96 | 28 / 8 | |
| 0.0.95 | 28 / 7 | |
| 0.0.94 | 29 / 7 | |
| 0.0.93 | 29 / 7 | |
| 0.0.92 | 29 / 7 | |
| 0.0.91 | 29 / 7 | |
| 0.0.90 | 29 / 7 | |
| 0.0.89 | 29 / 7 | |
| 0.0.88 | 29 / 7 | |
| 0.0.87 | 45 / 7 | |
| 0.0.86 | 45 / 7 | |
| 0.0.85 | 45 / 7 | |
| 0.0.84 | 45 / 7 | |
| 0.0.79 | 45 / 7 | |
| 0.0.76 | 45 / 7 | |
| 0.0.70 | 45 / 7 | |
| 0.0.67 | 45 / 7 | |
| 0.0.64 | 9 / 5 | |
| 0.0.63 | 9 / 5 | |
| 0.0.62 | 9 / 5 | |
| 0.0.61 | 9 / 5 | |
| 0.0.60 | 9 / 5 | |
| 0.0.59 | 9 / 5 | |
| 0.0.58 | 9 / 5 | |
| 0.0.57 | 9 / 5 | |
| 0.0.56 | 2 / 3 | |
| 0.0.55 | 2 / 3 | |
| 0.0.54 | 2 / 3 |
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.