@telia-ace/widget-components-widget-header-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@telia-ace/widget-core-flamingo | AI (phantom-deps): Same-org monorepo dep; phantom-dep false positive stable across versions. | ai | |
| phantom-deps | phantom-dep:@teliads/icons | AI (phantom-deps): Org-internal design system dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@teliads/components | AI (phantom-deps): Org-internal design system dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:lit-html | AI (phantom-deps): Lit ecosystem dep referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lit-labs/motion | AI (phantom-deps): Lit ecosystem dep referenced in config files; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.138 | 7 / 0 | |
| 1.1.137 | 7 / 0 | |
| 1.1.136 | 7 / 0 | |
| 1.1.135 | 7 / 0 | |
| 1.1.134 | 7 / 0 | |
| 1.1.133 | 7 / 0 | |
| 1.1.132 | 7 / 0 | |
| 1.1.131 | 7 / 0 | |
| 1.1.130 | 7 / 0 | |
| 1.1.124 | 7 / 0 | |
| 1.1.123 | 7 / 0 | |
| 1.1.122 | 7 / 0 | |
| 1.1.121 | 7 / 0 | |
| 1.1.120 | 7 / 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.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.