@telia-ace/widget-conversation-flamingo
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 | publisher-changed | AI (provenance): New publisher andreas.boukaras has strong track record (57 approved); transition appears legitimate with no code changes. | ai | |
| dependencies | unvetted-dep:@teliads/icons | AI (dependencies): First-party Telia design-system dep; consistent with this org-scoped widget package across all versions. | ai | |
| dependencies | unvetted-dep:@teliads/components | AI (dependencies): First-party Telia design-system dep; consistent with this org-scoped widget package across all versions. | ai | |
| phantom-deps | phantom-dep:marked | AI (phantom-deps): Referenced in config files; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:lit-html | AI (phantom-deps): Referenced in config files; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:dompurify | AI (phantom-deps): Referenced in config files; phantom-dep heuristic false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal enterprise widget package; missing metadata is expected, not indicative of spam/malware. | ai | |
| phantom-deps | phantom-dep:@lit-labs/motion | AI (phantom-deps): Referenced in config files; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@teliads/components | AI (phantom-deps): Referenced in config files; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@telia-ace/widget-core-flamingo | AI (phantom-deps): Same-org dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@teliads/icons | AI (phantom-deps): Referenced in config files; phantom-dep heuristic false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal package; missing description is consistent across 747 versions. | ai | |
| provenance | no-provenance | AI (provenance): Internal org package; no provenance is consistent with their publishing workflow. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.1.138 | 9 / 0 | |
| 1.1.137 | 9 / 0 | |
| 1.1.136 | 9 / 0 | |
| 1.1.135 | 9 / 0 | |
| 1.1.134 | 9 / 0 | |
| 1.1.133 | 9 / 0 | |
| 1.1.132 | 9 / 0 | |
| 1.1.131 | 9 / 0 | |
| 1.1.130 | 9 / 0 | |
| 1.1.129 | 9 / 0 | |
| 1.1.128 | 9 / 0 | |
| 1.1.127 | 9 / 0 | |
| 1.1.126 | 9 / 0 | |
| 1.1.125 | 9 / 0 | |
| 1.1.124 | 9 / 0 | |
| 1.1.123 | 9 / 0 | |
| 1.1.122 | 9 / 0 | |
| 1.1.121 | 9 / 0 | |
| 1.1.120 | 9 / 0 | |
| 1.1.119 | 8 / 0 | |
| 1.1.118 | 8 / 0 | |
| 1.1.117 | 8 / 0 | |
| 1.1.116 | 8 / 0 |
v1.1.138
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.135
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.134
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.133
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.132
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.131
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.130
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.129
2 findingsThis version was published by a different npm account than previous versions on 2026-01-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.128
2 findingsThis version was published by a different npm account than previous versions on 2026-01-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.127
2 findingsThis version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.126
2 findingsThis version was published by a different npm account than previous versions on 2025-12-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.125
2 findingsThis version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.124
2 findingsThis version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.123
2 findingsThis version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.122
2 findingsThis version was published by a different npm account than previous versions on 2025-08-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.