@boostxyz/boost-ui
## Best Practice
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/components/Avatar/Avatar.cjs | AI (source-diff): Standard tsup minified build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Dialog/Dialog.js | AI (source-diff): Standard tsup minified ESM build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Skeleton/BaseSkeleton.js | AI (source-diff): Standard tsup minified ESM build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Dialog/BaseDialog.js | AI (source-diff): Standard tsup minified ESM build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Avatar/BaseAvatar.js | AI (source-diff): Standard tsup minified ESM build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Avatar/Avatar.js | AI (source-diff): Standard tsup minified ESM build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Skeleton/Skeleton.cjs | AI (source-diff): Standard tsup minified build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Skeleton/index.cjs | AI (source-diff): Standard tsup minified build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Dialog/index.cjs | AI (source-diff): Standard tsup minified build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Avatar/index.cjs | AI (source-diff): Standard tsup minified build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Dialog/Dialog.cjs | AI (source-diff): Standard tsup minified build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Skeleton/BaseSkeleton.cjs | AI (source-diff): Standard tsup minified build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Dialog/BaseDialog.cjs | AI (source-diff): Standard tsup minified build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Avatar/BaseAvatar.cjs | AI (source-diff): Standard tsup minified build output for Radix UI component. | ai | |
| source-diff | obfuscated-file:dist/components/Accordion/BaseAccordion.cjs | AI (source-diff): Standard tsup minified bundle output for a React UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/components/Accordion/index.js | AI (source-diff): Standard tsup minified bundle output for a React UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/components/Accordion/BaseAccordion.js | AI (source-diff): Standard tsup minified bundle output for a React UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/components/Accordion/Accordion.js | AI (source-diff): Standard tsup minified bundle output for a React UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/components/Accordion/index.cjs | AI (source-diff): Standard tsup minified bundle output for a React UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/components/Accordion/Accordion.cjs | AI (source-diff): Standard tsup minified bundle output for a React UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/components/IconOrAvatar/IconOrAvatar.cjs | AI (source-diff): Standard tsup minified build output; imports only @radix-ui/react-avatar and react, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/components/IconOrAvatar/index.js | AI (source-diff): Standard tsup minified ESM build output; imports only @radix-ui/react-avatar and react, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/components/IconOrAvatar/IconOrAvatar.js | AI (source-diff): Standard tsup minified ESM build output; imports only @radix-ui/react-avatar and react, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/components/IconOrAvatar/BaseIconOrAvatar.js | AI (source-diff): Standard tsup minified ESM build output; imports only @radix-ui/react-avatar and react, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/components/IconOrAvatar/index.cjs | AI (source-diff): Standard tsup minified build output; imports only @radix-ui/react-avatar and react, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/components/IconOrAvatar/BaseIconOrAvatar.cjs | AI (source-diff): Standard tsup minified build output; imports only @radix-ui/react-avatar and react, no malicious patterns. | ai | |
| provenance | publisher-changed | AI (provenance): jamieboost is an established publisher (54 approved/0 rejected) within the boostxyz org; transition from moimikey appears to be a legitimate organizational maintainer handoff. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): vaul is a well-known legitimate React drawer library by emilkowalski; adding it to a UI component library is expected and benign. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jamieboost added within the @boostxyz org by a publisher with clean track record; routine team expansion for an established UI library. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop from 4MB to 266KB reflects removal of bloated artifacts/bundled output; consistent with package restructuring, not code replacement. | ai | |
| source-diff | large-new-source-files | AI (source-diff): UI component library using shadcn pattern; adding many component files is expected as the library grows. | ai | |
| dependencies | unvetted-dep:class-variance-authority | AI (dependencies): class-variance-authority (CVA) is a widely-used library for component variant management. Standard dependency for shadcn/ui-style component libraries. | ai | |
| dependencies | unvetted-dep:tailwindcss-animate | AI (dependencies): tailwindcss-animate is a common Tailwind CSS animation plugin. Expected dependency for a Tailwind-based UI library. | ai | |
| dependencies | unvetted-dep:tailwind-merge | AI (dependencies): tailwind-merge is a well-known, widely-used utility for merging Tailwind CSS classes. Stable false positive for this UI library package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-avatar | AI (phantom-deps): Radix UI components may be referenced in config/barrel files without direct imports in every source file. Normal pattern for a component library. | ai | |
| phantom-deps | phantom-dep:tailwindcss-animate | AI (phantom-deps): Tailwind plugins are referenced in config files (tailwind.config.ts) rather than direct JS imports — this is the expected usage pattern for Tailwind plugins. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-progress | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-tooltip | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-toggle | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-switch | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-select | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-dialog | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-avatar | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai | |
| dependencies | unvetted-dep:@tanstack/react-table | AI (dependencies): TanStack Table is a widely-used, well-maintained React table library with no known security issues. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-icons | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-tabs | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai | |
| dependencies | unvetted-dep:sonner | AI (dependencies): sonner is a legitimate, popular React toast notification library. Not a security risk for this UI package. | ai | |
| dependencies | unvetted-dep:vaul | AI (dependencies): vaul is a legitimate, widely-used React drawer component library. Not a security risk for this UI package. | ai | |
| provenance | no-provenance | AI (provenance): Lack of provenance is common (~88% of npm packages); no other risk signals present to elevate this concern. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-switch | AI (phantom-deps): Declared as a dependency and referenced in config files; common pattern in UI libraries. Not a security concern. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-table | AI (phantom-deps): Declared as a dependency and referenced in config files; common pattern in UI libraries. Not a security concern. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-dropdown-menu | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-toggle-group | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-separator | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-accordion | AI (dependencies): Part of the well-known @radix-ui primitive library used extensively in React UI development. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.15.1 | 19 / 19 | |
| 0.15.0 | 19 / 19 | |
| 0.14.0 | 19 / 19 | |
| 0.13.2 | 19 / 19 | |
| 0.13.1 | 19 / 19 | |
| 0.13.0 | 19 / 19 | |
| 0.12.1 | 19 / 19 | |
| 0.12.0 | 19 / 19 | |
| 0.11.2 | 19 / 19 | |
| 0.11.1 | 19 / 19 | |
| 0.11.0 | 19 / 19 | |
| 0.10.3 | 18 / 19 | |
| 0.10.2 | 18 / 19 | |
| 0.10.1 | 18 / 19 | |
| 0.9.2 | 18 / 19 | |
| 0.9.1 | 18 / 19 | |
| 0.9.0 | 18 / 19 | |
| 0.8.0 | 18 / 19 | |
| 0.7.0 | 18 / 19 | |
| 0.6.0 | 18 / 19 | |
| 0.5.3 | 17 / 19 | |
| 0.5.2 | 17 / 19 | |
| 0.5.1 | 17 / 19 | |
| 0.4.0 | 15 / 19 | |
| 0.2.6 | 14 / 19 | |
| 0.2.5 | 14 / 19 | |
| 0.2.4 | 14 / 19 | |
| 0.2.3 | 13 / 19 | |
| 0.2.2 | 12 / 19 | |
| 0.2.1 | 12 / 19 | |
| 0.2.0 | 12 / 19 | |
| 0.1.1 | 12 / 19 | |
| 0.1.0 | 16 / 15 |
v0.15.1
2 findingsThis version was published by a different npm account than previous versions on 2024-12-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
2 findingsThis version was published by a different npm account than previous versions on 2024-12-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jamieboost) than the most recent previously approved version (moimikey) on 2024-11-22, but jamieboost 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.
v0.13.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (moimikey) than the most recent previously approved version (jamieboost) on 2024-11-22, but moimikey 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.
v0.12.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (moimikey) than the most recent previously approved version (jamieboost) on 2024-11-15, but moimikey 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.
v0.12.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (moimikey) than the most recent previously approved version (jamieboost) on 2024-11-13, but moimikey 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.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jamieboost) than the most recent previously approved version (moimikey) on 2024-11-12, but jamieboost 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.
v0.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (moimikey) than the most recent previously approved version (jamieboost) on 2024-11-05, but moimikey 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.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jamieboost) than the most recent previously approved version (moimikey) on 2024-11-01, but jamieboost 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.
v0.8.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jamieboost) than the most recent previously approved version (moimikey) on 2024-11-01, but jamieboost 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.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
28 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
30 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-10-16. This could indicate a legitimate maintainer transition or an account compromise.
v0.5.1
29 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
26 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-10-15. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.6
13 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
13 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
13 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
7 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.
Newly 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.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
7 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.
Newly 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.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.