@telia-ace/widget-services
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped internal package in a 317-version org namespace; sparse metadata is a namespace-wide pattern, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across the @telia-ace namespace; not a malice signal for this org. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the entire @telia-ace namespace; stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.3.42 | 2 / 0 | |
| 1.3.41 | 2 / 0 | |
| 1.3.40 | 2 / 0 | |
| 1.3.39 | 2 / 0 | |
| 1.3.38 | 2 / 0 | |
| 1.3.37 | 2 / 0 | |
| 1.3.36 | 2 / 0 | |
| 1.3.35 | 2 / 0 | |
| 1.3.30 | 2 / 0 | |
| 1.3.29 | 2 / 0 | |
| 1.3.28 | 2 / 0 |
v1.3.42
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (teliajm) than the most recent previously approved version (andreas.boukaras) on 2026-05-28, but teliajm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.29
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.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.