@telia-ace/widget-conversational-hub
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:lit | AI (phantom-deps): Declared in dependencies; used transitively via @telia-ace scoped packages. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): Declared in dependencies; used transitively via @telia-ace scoped packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org package; missing repo/description/keywords typical for scoped internal libraries. | ai | |
| phantom-deps | phantom-dep:@telia-ace/widget-core-flamingo | AI (phantom-deps): Same-org scoped dep; phantom-dep false positive for monorepo-style package. | ai | |
| phantom-deps | phantom-dep:@telia-ace/widget-conversation-flamingo | AI (phantom-deps): Same-org scoped dep; phantom-dep false positive for monorepo-style package. | ai | |
| phantom-deps | phantom-dep:@lit/context | AI (phantom-deps): Declared in package.json deps; likely re-exported or used indirectly in build output. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.1.139 | 5 / 0 | |
| 1.1.138 | 5 / 0 | |
| 1.1.137 | 5 / 0 | |
| 1.1.136 | 5 / 0 | |
| 1.1.135 | 5 / 0 | |
| 1.1.134 | 5 / 0 | |
| 1.1.133 | 5 / 0 | |
| 1.1.132 | 5 / 0 | |
| 1.1.131 | 5 / 0 | |
| 1.1.130 | 5 / 0 | |
| 1.1.129 | 5 / 0 | |
| 1.1.128 | 5 / 0 | |
| 1.1.127 | 5 / 0 | |
| 1.1.126 | 5 / 0 | |
| 1.1.125 | 5 / 0 | |
| 1.1.124 | 5 / 0 | |
| 1.1.123 | 5 / 0 | |
| 1.1.122 | 5 / 0 | |
| 1.1.121 | 5 / 0 | |
| 1.1.120 | 5 / 0 | |
| 1.1.119 | 5 / 0 | |
| 1.1.118 | 5 / 0 | |
| 1.1.117 | 5 / 0 | |
| 1.1.116 | 5 / 0 |
v1.1.139
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (donami) than the most recent previously approved version (andreas.boukaras) on 2026-06-17, but donami is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.137
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.136
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.127
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.126
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.