@telia-ace/widget-components-copyright-flamingo
25
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, so a manually published version cannot be tied back to a reviewed commit.
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:copyright-CbKrN8bA.js | AI (source-diff): Minified build artifact from an established widget component pipeline; no malicious patterns in sampled code. | ai | |
| source-diff | obfuscated-file:copyright-0FDIxl4o.js | AI (source-diff): Minified build artifact; content is standard RxJS/Lit bundle output, not obfuscated malware. Consistent across 740 versions. | ai | |
| source-diff | obfuscated-file:copyright-BL_b6pIc.js | AI (source-diff): File is a standard Rollup/Vite CJS bundle; minified but not obfuscated — normal build output for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org package (@telia-ace scope) with 740 versions; sparse metadata is a consistent pattern across the package family, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:@telia-ace/widget-core-flamingo | AI (phantom-deps): Same org-scope sibling dependency; phantom-dep heuristic is a stable false positive for this package family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with the @telia-ace internal package pattern across all 740 versions. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present to elevate this. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.1.139 | 2 / 0 | |
| 1.1.138 | 2 / 0 | |
| 1.1.137 | 2 / 0 | |
| 1.1.136 | 2 / 0 | |
| 1.1.135 | 2 / 0 | |
| 1.1.134 | 2 / 0 | |
| 1.1.133 | 2 / 0 | |
| 1.1.132 | 2 / 0 | |
| 1.1.131 | 2 / 0 | |
| 1.1.130 | 2 / 0 | |
| 1.1.129 | 2 / 0 | |
| 1.1.128 | 2 / 0 | |
| 1.1.127 | 2 / 0 | |
| 1.1.126 | 2 / 0 | |
| 1.1.125 | 2 / 0 | |
| 1.1.124 | 2 / 0 | |
| 1.1.123 | 2 / 0 | |
| 1.1.121 | 2 / 0 | |
| 1.1.120 | 2 / 0 | |
| 1.1.119 | 2 / 0 | |
| 1.1.118 | 2 / 0 | |
| 1.1.117 | 2 / 0 | |
| 1.1.116 | 2 / 0 | |
| 1.1.69 | 2 / 0 | |
| 1.1.68 | 2 / 0 |
v1.1.69
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.68
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.