@telia-ace/widget-side-menu
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal org widget package; missing description is a stable pattern across this package family. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all 433 versions; stable org publishing pattern, not a new anomaly. | ai | |
| phantom-deps | phantom-dep:@teliads/components | AI (phantom-deps): Likely used transitively or in config; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal enterprise widget package in a large monorepo; missing metadata is a style issue, not a spam/malware signal. | ai | |
| phantom-deps | phantom-dep:@lit-labs/motion | AI (phantom-deps): Lit ecosystem peer; referenced in config, stable false positive. | ai | |
| phantom-deps | phantom-dep:lit-html | AI (phantom-deps): Lit ecosystem peer; referenced in config, stable false positive. | ai | |
| phantom-deps | phantom-dep:@telia-ace/widget-core-flamingo | AI (phantom-deps): Same-org scoped dependency; phantom-dep heuristic is a stable false positive for this monorepo pattern. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.1.138 | 6 / 0 | |
| 1.1.137 | 6 / 0 | |
| 1.1.136 | 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.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.