@adia-ai/web-components
AdiaUI web components — vanilla custom elements. A2UI runtime (renderer, registry, streams, wiring) lives in @adia-ai/a2ui-utils.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/prose.sheet.js | AI (source-diff): Auto-generated CSS-in-JS bundle; same pattern as host.sheet.js, purely CSS content. | ai | |
| source-diff | encoded-string-file:dist/web-components.min.js | AI (source-diff): Long strings are minified UI component logic (DOM manipulation, template rendering); no exfiltration or obfuscated payload. | ai | |
| phantom-deps | phantom-dep:@phosphor-icons/core | AI (phantom-deps): Icons dep used via core/icons-phosphor.js sideEffect; heuristic false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/host.sheet.js | AI (source-diff): Auto-generated CSS-in-JS bundle (minified CSS string); build comment confirms origin, no executable payload. | ai | |
| source-diff | obfuscated-file:dist/web-components.sheet.js | AI (source-diff): Auto-generated CSS-in-JS bundle; same pattern, no malicious indicators. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @adia-ai/a2ui-runtime is a first-party sibling package explicitly described in package.json; not a suspicious third-party addition. | ai | |
| provenance | no-provenance | AI (provenance): New package from a small org; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 51 of 165)
| Version | Deps | Published |
|---|---|---|
| 0.8.10 | 8 / 0 | |
| 0.8.9 | 8 / 0 | |
| 0.8.8 | 8 / 0 | |
| 0.8.7 | 8 / 0 | |
| 0.8.6 | 8 / 0 | |
| 0.8.5 | 8 / 0 | |
| 0.8.4 | 8 / 0 | |
| 0.8.3 | 8 / 0 | |
| 0.8.2 | 8 / 0 | |
| 0.8.1 | 8 / 0 | |
| 0.8.0 | 8 / 0 | |
| 0.7.28 | 8 / 0 | |
| 0.7.27 | 8 / 0 | |
| 0.7.26 | 8 / 0 | |
| 0.7.25 | 8 / 0 | |
| 0.7.24 | 8 / 0 | |
| 0.7.23 | 7 / 0 | |
| 0.7.22 | 7 / 0 | |
| 0.7.21 | 7 / 0 | |
| 0.7.20 | 7 / 0 | |
| 0.7.19 | 7 / 0 | |
| 0.7.18 | 7 / 0 | |
| 0.7.17 | 7 / 0 | |
| 0.7.16 | 7 / 0 | |
| 0.7.15 | 7 / 0 | |
| 0.7.14 | 7 / 0 | |
| 0.7.13 | 7 / 0 | |
| 0.7.12 | 7 / 0 | |
| 0.7.11 | 7 / 0 | |
| 0.7.10 | 7 / 0 | |
| 0.7.9 | 7 / 0 | |
| 0.7.8 | 7 / 0 | |
| 0.7.7 | 7 / 0 | |
| 0.7.6 | 7 / 0 | |
| 0.7.5 | 7 / 0 | |
| 0.7.4 | 7 / 0 | |
| 0.7.3 | 7 / 0 | |
| 0.7.2 | 7 / 0 | |
| 0.7.1 | 7 / 0 | |
| 0.7.0 | 7 / 0 | |
| 0.6.50 | 7 / 0 | |
| 0.6.49 | 7 / 0 | |
| 0.6.48 | 7 / 0 | |
| 0.6.47 | 7 / 0 | |
| 0.6.46 | 7 / 0 | |
| 0.6.45 | 7 / 0 | |
| 0.6.44 | 7 / 0 | |
| 0.6.43 | 7 / 0 | |
| 0.6.42 | 7 / 0 | |
| 0.6.41 | 7 / 0 | |
| 0.6.40 | 7 / 0 |
v0.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
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.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
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.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.