@telia-ace/widget-components-area-flamingo No license 22 versions

@telia-ace/widget-components-area-flamingo

npm

22

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

anhe92andreas.boukarasbratnteliajonasrosenlindteliajmdonami

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:area-Muu1scep.js	AI (source-diff): Minified Lit framework bundle; not obfuscated malware. Stable pattern for this component library.	ai	2026/05/12
source-diff	obfuscated-file:area-DyeEuDGW.js	AI (source-diff): Long lines are minified Lit framework output (Google BSD-3-Clause), not obfuscation; stable pattern for this build pipeline.	ai	2026/05/12
source-diff	obfuscated-file:area-CQnjsNMv.js	AI (source-diff): File is minified Lit framework bundle with Google BSD-3-Clause license header; standard build output for this UI component library.	ai	2026/05/06
bogus-package	bogus-package	AI (bogus-package): Internal scoped package with 687 versions and ~3yr history; missing metadata is consistent with private org packages, not spam.	ai	2026/04/30
npm-metadata	no-description	AI (npm-metadata): Stable internal org package; missing description is a style choice, not a risk indicator.	ai	2026/04/30
phantom-deps	phantom-dep:@telia-ace/widget-core-flamingo	AI (phantom-deps): Same org scope dependency; phantom-dep heuristic is unreliable for re-exported or type-only deps in component libraries.	ai	2026/04/30

Versions (showing 22 of 22)

Version	Deps	Published
1.1.138	2 / 0	2026-05-07
1.1.137	2 / 0	2026-04-24
1.1.136	2 / 0	2026-04-24
1.1.135	2 / 0	2026-03-20
1.1.134	2 / 0	2026-03-16
1.1.133	2 / 0	2026-03-13
1.1.132	2 / 0	2026-03-13
1.1.131	2 / 0	2026-03-10
1.1.130	2 / 0	2026-02-18
1.1.129	2 / 0	2026-01-27
1.1.128	2 / 0	2026-01-13
1.1.127	2 / 0	2026-01-08
1.1.126	2 / 0	2025-12-18
1.1.125	2 / 0	2025-12-16
1.1.124	2 / 0	2025-12-16
1.1.123	2 / 0	2025-12-16
1.1.121	2 / 0	2025-08-13
1.1.120	2 / 0	2025-08-08
1.1.119	2 / 0	2025-05-08
1.1.118	2 / 0	2025-05-08
1.1.117	2 / 0	2025-05-02
1.1.116	2 / 0	2025-05-02

v1.1.138

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.137

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.136

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.135

2 findings

HIGH New obfuscated file: area-CQnjsNMv.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.134

2 findings

HIGH New obfuscated file: area-CQnjsNMv.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.133

2 findings

HIGH New obfuscated file: area-CQnjsNMv.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.132

2 findings

HIGH New obfuscated file: area-CQnjsNMv.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.131

2 findings

HIGH New obfuscated file: area-CQnjsNMv.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.130

2 findings

HIGH New obfuscated file: area-CQnjsNMv.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.129

2 findings

HIGH New obfuscated file: area-CQnjsNMv.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.128

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.127

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.126

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.125

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.124

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.123

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.121

2 findings

HIGH New obfuscated file: area-Muu1scep.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.120

2 findings

HIGH New obfuscated file: area-DyeEuDGW.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.119

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.118

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.117

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.116

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.