@docyrus/ui-pro-ai-assistant
Docyrus AI Assistant component — full-featured chat UI with canvas, projects, and i18n support.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm packages); no other risk signals elevate this. | ai | |
| dependencies | unvetted-dep:xlsx | AI (dependencies): xlsx is a widely-used spreadsheet library; its use here is consistent with a document/canvas UI component. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): clsx is a utility commonly used in Tailwind config/class helpers; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): tailwind-merge used in config/class utilities; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@platejs/diff | AI (phantom-deps): Large UI component library; deps declared for consumers, not all directly imported in entry. | ai | |
| phantom-deps | phantom-dep:scroll-into-view-if-needed | AI (phantom-deps): Same pattern — declared for consumer use, not directly imported in main entry. | ai | |
| phantom-deps | phantom-dep:react-day-picker | AI (phantom-deps): Same pattern — declared for consumer use, not directly imported in main entry. | ai | |
| phantom-deps | phantom-dep:@univerjs/thread-comment | AI (phantom-deps): Same pattern — declared for consumer use, not directly imported in main entry. | ai | |
| phantom-deps | phantom-dep:@visactor/vtable-plugins | AI (phantom-deps): Same pattern — declared for consumer use, not directly imported in main entry. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 110 / 8 | |
| 0.6.8 | 110 / 8 | |
| 0.6.7 | 102 / 8 | |
| 0.6.5 | 102 / 8 | |
| 0.5.7 | 102 / 8 | |
| 0.5.4 | 102 / 8 | |
| 0.5.3 | 102 / 8 | |
| 0.5.2 | 102 / 8 | |
| 0.4.6 | 102 / 8 | |
| 0.4.5 | 102 / 8 | |
| 0.4.4 | 102 / 8 | |
| 0.3.7 | 101 / 8 | |
| 0.3.3 | 101 / 8 | |
| 0.2.1 | 101 / 8 | |
| 0.1.9 | 101 / 8 |
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
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.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.