@telia-ace/widget-conversational-agent
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/context | AI (phantom-deps): Config-file reference in scoped org package; stable pattern. | ai | |
| phantom-deps | phantom-dep:@telia-ace/widget-core-flamingo | AI (phantom-deps): Internal org dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@telia-ace/widget-conversation-flamingo | AI (phantom-deps): Internal org dependency; stable for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.1.138
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.134
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.132
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.130
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.129
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.128
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.