@atom8n/chat
This is an embeddable Chat widget for n8n. It allows the execution of AI-Powered Workflows through a Chat window.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atom8n/design-system | AI (phantom-deps): Same-org scoped dep; phantom-dep false positive for a component library using catalog: version references. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Vue component library; deps referenced in build/config files, not direct imports — stable false positive. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): Same pattern: build/config reference in Vue component library. | ai | |
| phantom-deps | phantom-dep:highlight.js | AI (phantom-deps): Same pattern: build/config reference in Vue component library. | ai | |
| typosquat | typosquat.levenshtein:chalk | AI (typosquat): @atom8n/chat is a scoped Vue chat component; no semantic resemblance to chalk despite edit distance. | ai | |
| phantom-deps | phantom-dep:vue-markdown-render | AI (phantom-deps): Same pattern: build/config reference in Vue component library. | ai | |
| phantom-deps | phantom-dep:markdown-it-link-attributes | AI (phantom-deps): Same pattern: build/config reference in Vue component library. | ai | |
| phantom-deps | phantom-dep:@n8n/design-system | AI (phantom-deps): Same pattern: build/config reference in Vue component library. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.5.7 | 7 / 13 | |
| 1.5.6 | 7 / 13 | |
| 1.5.5 | 7 / 13 | |
| 1.5.4 | 7 / 13 | |
| 1.5.3 | 7 / 13 | |
| 1.5.2 | 7 / 13 | |
| 1.5.1 | 7 / 13 | |
| 1.5.0 | 7 / 13 | |
| 1.4.3 | 7 / 13 | |
| 1.4.2 | 7 / 13 | |
| 1.4.1 | 7 / 13 | |
| 1.4.0 | 7 / 13 | |
| 1.3.0 | 7 / 13 | |
| 1.2.9 | 7 / 13 | |
| 1.2.8 | 7 / 13 | |
| 1.2.7 | 7 / 13 | |
| 1.2.6 | 7 / 13 | |
| 1.2.5 | 7 / 13 | |
| 1.2.4 | 7 / 13 | |
| 1.2.3 | 7 / 13 | |
| 1.2.2 | 7 / 13 | |
| 1.2.1 | 7 / 13 | |
| 1.2.0 | 7 / 13 |
v1.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.