@stagewise/toolbar
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/panel-D3CHoSfg.cjs | AI (source-diff): Minified Preact hooks/panel CJS bundle; standard build output for this UI toolkit package. | ai | |
| source-diff | obfuscated-file:dist/panel-CBp9itVW.cjs | AI (source-diff): Minified Preact UI panel CJS bundle; standard Vite build output for this package. | ai | |
| source-diff | obfuscated-file:dist/jsx-runtime-r6LeVNNi.cjs | AI (source-diff): Minified Preact JSX runtime bundle; standard build output for this package. | ai | |
| source-diff | obfuscated-file:dist/panel-IzqaHDKs.cjs | AI (source-diff): Minified Preact component bundle; standard build output for this package. | ai | |
| phantom-deps | phantom-dep:preact | AI (phantom-deps): Declared dependency; used in runtime code. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:zustand | AI (phantom-deps): Declared dependency; used in runtime code. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:superjson | AI (phantom-deps): Declared dependency; used in runtime code. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): Build tool in dependencies; used in build config. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): Declared dependency; used in runtime code. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:ua-parser-js | AI (phantom-deps): Declared dependency; used in runtime code. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@preact/compat | AI (phantom-deps): Declared dependency; used in runtime code. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Declared dependency; used in runtime code. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@headlessui/react | AI (phantom-deps): Declared dependency; used in runtime code. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:javascript-time-ago | AI (phantom-deps): Declared dependency; used in runtime code. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-remove-scroll | AI (phantom-deps): Declared dependency; used in runtime code. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:postcss-prefix-selector | AI (phantom-deps): Declared dependency; used in build config. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:vite-plugin-css-injected-by-js | AI (phantom-deps): Declared dependency; used in build config. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Declared dependency; used in runtime code. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared dependency; used in runtime code and configs. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tsup | AI (phantom-deps): Build tool in dependencies; used in build config. Stable pattern for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.6.3 | 0 / 31 | |
| 0.6.2 | 0 / 31 | |
| 0.6.1 | 0 / 31 | |
| 0.6.0 | 0 / 31 | |
| 0.5.2 | 0 / 28 | |
| 0.5.1 | 0 / 28 | |
| 0.5.0 | 0 / 28 | |
| 0.4.9 | 0 / 24 | |
| 0.4.8 | 0 / 24 | |
| 0.4.7 | 0 / 24 | |
| 0.4.6 | 0 / 24 | |
| 0.4.5 | 0 / 24 | |
| 0.4.4 | 0 / 28 | |
| 0.4.3 | 0 / 28 | |
| 0.4.2 | 0 / 28 | |
| 0.4.1 | 0 / 28 | |
| 0.4.0 | 0 / 28 | |
| 0.3.1 | 0 / 28 | |
| 0.3.0 | 0 / 28 | |
| 0.2.1 | 16 / 12 | |
| 0.2.0 | 16 / 12 | |
| 0.1.0 | 16 / 12 |
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
3 findingsNewly 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.4.8
3 findingsNewly 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.4.7
3 findingsNewly 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.4.6
3 findingsNewly 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.4.5
3 findingsNewly 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.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
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.