@telia-ace/ace-chat-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): andreas.boukaras is an established publisher in the @telia-ace org with 57 approved packages; transition appears legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Org-scoped internal component; missing metadata is a style issue, not a malice indicator across 663 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this package family; not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across entire version history; common for this publisher. | ai | |
| phantom-deps | phantom-dep:@telia-ace/widget-core-flamingo | AI (phantom-deps): Same-org sibling dep; phantom-dep false positive for monorepo publish pattern. | ai | |
| phantom-deps | phantom-dep:@telia-ace/widget-conversation-flamingo | AI (phantom-deps): Same-org sibling dep; phantom-dep false positive for monorepo publish pattern. | ai | |
| phantom-deps | phantom-dep:@teliads/icons | AI (phantom-deps): Telia design system icons dep; referenced in config, stable false positive. | ai | |
| phantom-deps | phantom-dep:@lit/context | AI (phantom-deps): Lit framework peer dep; referenced in config, stable false positive. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.1.138 | 6 / 0 | |
| 1.1.137 | 6 / 0 | |
| 1.1.136 | 6 / 0 | |
| 1.1.135 | 6 / 0 | |
| 1.1.134 | 6 / 0 | |
| 1.1.133 | 6 / 0 | |
| 1.1.132 | 6 / 0 | |
| 1.1.131 | 6 / 0 | |
| 1.1.130 | 6 / 0 | |
| 1.1.129 | 6 / 0 | |
| 1.1.128 | 6 / 0 | |
| 1.1.127 | 6 / 0 | |
| 1.1.126 | 6 / 0 | |
| 1.1.125 | 6 / 0 | |
| 1.1.124 | 6 / 0 | |
| 1.1.123 | 6 / 0 | |
| 1.1.122 | 6 / 0 | |
| 1.1.121 | 6 / 0 | |
| 1.1.120 | 6 / 0 | |
| 1.1.119 | 6 / 0 | |
| 1.1.118 | 6 / 0 | |
| 1.1.117 | 6 / 0 | |
| 1.1.116 | 6 / 0 |
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
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.