@dialpad/dialtone-vue
Vue component library for Dialpad's design system Dialtone
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:regex-combined-emojis | AI (phantom-deps): New emoji-regex replacement used indirectly. | ai | |
| phantom-deps | phantom-dep:emoji-toolkit | AI (phantom-deps): Used indirectly via config, longstanding dep. | ai | |
| source-diff | obfuscated-file:dist/chunks/index-lu2o2f4r.js | AI (source-diff): Same emoji-regex build artifact, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/chunks/index-GVD15GIB.js | AI (source-diff): Long lines are emoji unicode regex literals, not obfuscation. | ai | |
| dependencies | unvetted-dep:regex-combined-emojis | AI (dependencies): Emoji regex utility; appropriate for a rich-text editor component with emoji handling. | ai | |
| source-diff | obfuscated-file:dist/message_input-BiCHkV9g.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; code is readable Vue component logic, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/rich_text_editor-FduHYl-G.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; code is readable Tiptap/Vue component logic, not obfuscated malware. | ai | |
| dependencies | unvetted-dep:@dialpad/i18n | AI (dependencies): First-party Dialpad scoped package; stable dependency for this component library. | ai | |
| dependencies | unvetted-dep:emoji-toolkit | AI (dependencies): Well-known emoji utility library; appropriate for a UI component library with emoji support. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-list-item | AI (phantom-deps): Tiptap extensions bundled/re-exported by component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-bubble-menu | AI (phantom-deps): Tiptap extensions bundled/re-exported by component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-bullet-list | AI (phantom-deps): Tiptap extensions bundled/re-exported by component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-font-family | AI (phantom-deps): Tiptap extensions bundled/re-exported by component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-placeholder | AI (phantom-deps): Tiptap extensions bundled/re-exported by component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-ordered-list | AI (phantom-deps): Tiptap extensions bundled/re-exported by component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-floating-menu | AI (phantom-deps): Tiptap extensions bundled/re-exported by component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-history | AI (phantom-deps): Tiptap extensions bundled/re-exported by component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@tiptap/static-renderer | AI (phantom-deps): Tiptap extensions bundled/re-exported by component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-color | AI (phantom-deps): Tiptap extensions bundled/re-exported by component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:linkifyjs | AI (phantom-deps): Component library pattern; deps declared for consumers, not necessarily directly imported in analyzed entry. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 3.221.1 | 42 / 12 | |
| 3.221.0 | 42 / 12 | |
| 3.220.0 | 42 / 12 | |
| 3.219.4 | 42 / 12 | |
| 3.219.2 | 42 / 12 | |
| 3.219.1 | 42 / 12 | |
| 3.219.0 | 42 / 12 | |
| 3.218.5 | 42 / 12 | |
| 3.151.0 | 29 / 47 | |
| 3.150.1 | 29 / 47 | |
| 3.135.2 | 28 / 47 | |
| 3.135.1 | 28 / 47 | |
| 3.135.0 | 28 / 47 | |
| 3.134.0 | 28 / 47 | |
| 3.133.0 | 27 / 47 | |
| 3.132.1 | 27 / 46 | |
| 3.132.0 | 27 / 46 | |
| 3.131.0 | 27 / 46 | |
| 3.130.0 | 27 / 46 | |
| 3.129.2 | 27 / 46 | |
| 3.129.1 | 27 / 46 | |
| 3.129.0 | 27 / 46 | |
| 3.128.0 | 27 / 46 | |
| 3.127.0 | 27 / 46 | |
| 3.126.0 | 27 / 46 | |
| 3.125.1 | 27 / 46 | |
| 3.125.0 | 27 / 46 | |
| 3.124.0 | 27 / 46 | |
| 3.123.4 | 27 / 46 | |
| 3.123.3 | 27 / 46 | |
| 3.123.2 | 27 / 46 |
v3.151.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.150.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.135.2
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.
v3.135.1
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.
v3.135.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.
v3.134.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.
v3.133.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.
v3.132.1
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.
v3.132.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.
v3.131.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.
v3.130.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.
v3.129.2
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.
v3.129.1
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.
v3.129.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.
v3.128.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.
v3.127.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.126.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.125.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.125.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.124.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.123.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.123.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.123.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.