@telia-ace/widget-core-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal widget package; missing description is a stable pattern across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package with no public repo/keywords; not a spam indicator for this package. | ai | |
| provenance | no-provenance | AI (provenance): Internal package; no provenance is consistent across all 684 versions. | ai | |
| phantom-deps | phantom-dep:@lit/context | AI (phantom-deps): Internal widget package; phantom dep likely re-exported or used indirectly via build config. | ai | |
| phantom-deps | phantom-dep:@teliads/icons | AI (phantom-deps): Telia-branded icons dep; likely re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@lit-labs/motion | AI (phantom-deps): Internal widget package; dep likely used indirectly via build config. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 1.1.141 | 6 / 0 | |
| 1.1.140 | 6 / 0 | |
| 1.1.139 | 6 / 0 | |
| 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 | |
| 1.1.115 | 6 / 0 | |
| 1.1.114 | 6 / 0 | |
| 1.1.113 | 6 / 0 | |
| 1.1.112 | 6 / 0 | |
| 1.1.111 | 6 / 0 | |
| 1.1.110 | 6 / 0 | |
| 1.1.109 | 6 / 0 | |
| 1.1.108 | 6 / 0 | |
| 1.1.107 | 6 / 0 | |
| 1.1.106 | 6 / 0 | |
| 1.1.105 | 6 / 0 | |
| 1.1.104 | 6 / 0 | |
| 1.1.103 | 6 / 0 | |
| 1.1.102 | 6 / 0 | |
| 1.1.101 | 6 / 0 | |
| 1.1.100 | 6 / 0 | |
| 1.1.99 | 6 / 0 | |
| 1.1.98 | 6 / 0 | |
| 1.1.97 | 6 / 0 | |
| 1.1.96 | 6 / 0 | |
| 1.1.95 | 6 / 0 | |
| 1.1.94 | 6 / 0 | |
| 1.1.93 | 6 / 0 | |
| 1.1.92 | 6 / 0 | |
| 1.1.91 | 6 / 0 | |
| 1.1.90 | 6 / 0 | |
| 1.1.89 | 6 / 0 | |
| 1.1.88 | 6 / 0 | |
| 1.1.87 | 6 / 0 | |
| 1.1.86 | 6 / 0 | |
| 1.1.85 | 6 / 0 | |
| 1.1.84 | 6 / 0 | |
| 1.1.83 | 6 / 0 | |
| 1.1.82 | 6 / 0 | |
| 1.1.81 | 6 / 0 | |
| 1.1.80 | 6 / 0 | |
| 1.1.79 | 6 / 0 | |
| 1.1.78 | 6 / 0 | |
| 1.1.77 | 6 / 0 | |
| 1.1.76 | 6 / 0 | |
| 1.1.75 | 6 / 0 | |
| 1.1.71 | 6 / 0 | |
| 1.1.70 | 6 / 0 | |
| 1.1.69 | 6 / 0 | |
| 1.1.68 | 6 / 0 |
v1.1.141
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.108
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.69
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.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.