@murumets-ee/ticketing-ui
Ticketing inbox UI — ticket list, detail panel, reply composer, kanban board, and real-time updates.
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/ticket-list-Cyz17Q2A.mjs | AI (source-diff): Standard minified ESM bundle; content is clearly a ticket list UI component, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-CFOY8Fvr.mjs | AI (source-diff): Standard tsdown/ESM bundle output; samples show React/TipTap UI component code with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-CoC7sAIG.mjs | AI (source-diff): Standard tsdown minified ESM output; content is readable React UI component code. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-Dn2rxsOk.mjs | AI (source-diff): Standard tsdown minified ESM output; content is readable React UI component code. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-DecIkFrE.mjs | AI (source-diff): Rollup chunk with hashed name; readable imports from tiptap/lucide/react — normal build output. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-CDr11K59.mjs | AI (source-diff): Standard bundler minification output; code is readable React UI component logic. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-DDiVcEMT.mjs | AI (source-diff): Standard minified ESM build output; React component with tiptap/lucide imports, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-Be0Gri2T.mjs | AI (source-diff): Standard bundler minification; content clearly maps to tiptap/lucide-react UI code. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-Ds7Kbq9X.mjs | AI (source-diff): Standard minified React component bundle; samples show UI logic with known deps. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-Cg_aEv28.mjs | AI (source-diff): Standard minified bundle output from tsdown; content is readable React UI component code. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-DVYtjBO1.mjs | AI (source-diff): Standard minified bundle output from tsdown; content is readable React UI component code. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-DlWmijLx.mjs | AI (source-diff): Standard minified ESM bundle with tiptap/lucide/react imports; no obfuscation or exfiltration. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-Blx5s9Zf.mjs | AI (source-diff): Standard minified ESM bundle; readable symbols, no encoded payloads. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-EjZFr_J_.mjs | AI (source-diff): Standard minified React component bundle; samples show ticket list UI logic, no suspicious patterns. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-C85IBsF3.mjs | AI (source-diff): Standard tsdown-minified React component bundle; content is readable JSX logic, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-CNFtvxSb.mjs | AI (source-diff): Standard tsdown-minified React component bundle; content is readable JSX logic, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-lnZfdf6b.mjs | AI (source-diff): Standard minified ESM bundle output from tsdown; source maps present, imports are all known UI/React deps. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-eQgDHTLR.mjs | AI (source-diff): Standard minified ESM bundle output from tsdown; source maps present, imports are all known UI/React deps. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-BRTiTZmE.mjs | AI (source-diff): Standard tsdown minified ESM bundle; code is readable React UI component, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-DPuGAzxf.mjs | AI (source-diff): Standard minified ESM bundle; sample shows ticket list UI logic, no malicious patterns. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-image | AI (phantom-deps): Bundled package; TipTap deps consumed in dist output. | ai | |
| source-diff | obfuscated-file:dist/api-BlpGyjxI.mjs | AI (source-diff): Standard minified ESM bundle output from tsdown/Vite; code is readable UI/API logic with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-C40TlIFn.mjs | AI (source-diff): Standard minified ESM bundle; sample shows TipTap editor integration and React UI components, no malicious patterns. | ai | |
| phantom-deps | phantom-dep:@tiptap/pm | AI (phantom-deps): Bundled package; TipTap deps are consumed in dist, not directly imported in source files. | ai | |
| phantom-deps | phantom-dep:@tiptap/core | AI (phantom-deps): Bundled package; TipTap deps consumed in dist output. | ai | |
| phantom-deps | phantom-dep:@tiptap/react | AI (phantom-deps): Bundled package; TipTap deps consumed in dist output. | ai | |
| phantom-deps | phantom-dep:@tiptap/starter-kit | AI (phantom-deps): Bundled package; TipTap deps consumed in dist output. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-link | AI (phantom-deps): Bundled package; TipTap deps consumed in dist output. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-uZNLGplk.mjs | AI (source-diff): Standard tsdown/ESM bundle output; readable imports, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-Ccn5EaCg.mjs | AI (source-diff): Standard minified ESM bundle; code samples show normal React UI component logic with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-B2cltoQP.mjs | AI (source-diff): Standard tsdown-bundled ESM output; minified React component with tanstack-query/lucide-react imports. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-DaXbI3Bm.mjs | AI (source-diff): Standard tsdown-bundled ESM output; minified React component with lucide-react/next-intl/sanitize-html imports. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-DkT8WIsb.mjs | AI (source-diff): Standard minified ESM bundle from build tool; readable fetch/query logic, no malicious patterns. | ai | |
| phantom-deps | phantom-dep:sanitize-html | AI (phantom-deps): Used in bundled dist output; phantom-dep heuristic misses bundled imports. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-CVgFepky.mjs | AI (source-diff): Standard minified ESM bundle; sanitize-html usage visible, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-DsTowJP6.mjs | AI (source-diff): Minified React UI component; standard imports from lucide-react, react, next-intl. | ai | |
| phantom-deps | phantom-dep:@murumets-ee/admin-ui | AI (phantom-deps): Same-org dep likely consumed in build output. | ai | |
| phantom-deps | phantom-dep:@murumets-ee/queue | AI (phantom-deps): Same-org dep used in plugin.mjs dynamic import path. | ai | |
| phantom-deps | phantom-dep:@murumets-ee/ui | AI (phantom-deps): Same-org dep likely re-exported or used transitively in build output. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-DSN0H448.mjs | AI (source-diff): Minified React UI component; standard imports from lucide-react, react, @tanstack/react-query. | ai | |
| source-diff | obfuscated-file:dist/plugin.mjs | AI (source-diff): Minified tsdown build output; readable imports from same-org packages and React ecosystem. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-UysbN8ku.mjs | AI (source-diff): Standard tsdown/ESM bundle output; readable React UI code, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): Standard tsdown/ESM bundle output; readable React UI code, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-BKA08JUP.mjs | AI (source-diff): Standard tsdown/ESM bundle output; readable React UI code, no malicious patterns. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): clsx is used via bundler/config (cn utility); stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/ticket-detail-QVodNK9M.mjs | AI (source-diff): Standard bundler output; samples show ticket detail UI components with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/inbox.mjs | AI (source-diff): Standard bundler output (tsdown); code is readable React UI logic, not obfuscated malware. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): tailwind-merge used via cn utility in config; stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/ticket-list-BdG2GQCc.mjs | AI (source-diff): Standard bundler output; samples show ticket list UI components with no malicious patterns. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.25.0 | 15 / 16 | |
| 0.24.1 | 15 / 16 | |
| 0.24.0 | 15 / 16 | |
| 0.23.2 | 15 / 16 | |
| 0.23.1 | 15 / 16 | |
| 0.23.0 | 14 / 16 | |
| 0.22.1 | 14 / 16 | |
| 0.22.0 | 14 / 16 | |
| 0.21.1 | 14 / 16 | |
| 0.21.0 | 14 / 16 | |
| 0.20.0 | 14 / 16 | |
| 0.19.0 | 14 / 16 | |
| 0.18.0 | 14 / 16 | |
| 0.17.1 | 14 / 16 | |
| 0.17.0 | 14 / 16 | |
| 0.16.5 | 9 / 15 | |
| 0.16.4 | 9 / 15 | |
| 0.16.3 | 9 / 15 | |
| 0.16.2 | 9 / 15 | |
| 0.16.1 | 9 / 15 | |
| 0.16.0 | 9 / 15 | |
| 0.15.4 | 9 / 15 | |
| 0.15.3 | 9 / 15 | |
| 0.15.2 | 9 / 15 | |
| 0.15.1 | 9 / 15 | |
| 0.15.0 | 9 / 15 | |
| 0.14.0 | 9 / 15 | |
| 0.13.3 | 9 / 15 | |
| 0.13.2 | 9 / 15 | |
| 0.13.1 | 9 / 15 | |
| 0.13.0 | 9 / 15 | |
| 0.12.0 | 9 / 15 | |
| 0.11.0 | 8 / 14 | |
| 0.10.0 | 8 / 14 | |
| 0.9.0 | 8 / 14 | |
| 0.8.0 | 8 / 14 | |
| 0.7.0 | 8 / 14 | |
| 0.6.1 | 8 / 14 | |
| 0.6.0 | 8 / 14 | |
| 0.5.1 | 5 / 14 | |
| 0.5.0 | 5 / 14 | |
| 0.4.8 | 2 / 14 | |
| 0.4.7 | 2 / 14 | |
| 0.4.6 | 2 / 14 | |
| 0.4.5 | 2 / 14 | |
| 0.4.0 | 2 / 14 | |
| 0.3.0 | 2 / 14 | |
| 0.2.0 | 2 / 14 | |
| 0.1.5 | 2 / 11 | |
| 0.1.4 | 2 / 11 | |
| 0.1.3 | 2 / 11 |
v0.25.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
4 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.
Package 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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
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.3.0
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.2.0
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.1.5
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.