@elliemae/ds-icons
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon components as new files; pattern is stable for this package. | ai | |
| source-diff | obfuscated-file:dist/cjs/LockupLightBGICEBlack.js | AI (source-diff): SVG path data in bundled icon component, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/LockupLightBGICEBlack.js | AI (source-diff): SVG path data in bundled icon component, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/LockupLightBGICEBlue.js | AI (source-diff): SVG path data in bundled icon component, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/LockupLightBGICEBlue.js | AI (source-diff): SVG path data in bundled icon component, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/LockupDarkBGICEBlue.js | AI (source-diff): SVG path data in bundled icon component, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/LockupDarkBGICEBlue.js | AI (source-diff): SVG path data in bundled icon component, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/ConditionsPopout.js | AI (source-diff): Standard esbuild bundle output for SVG icon component; matches all other icons in this package. | ai | |
| source-diff | obfuscated-file:dist/cjs/ConditionsPopout.js | AI (source-diff): Standard esbuild bundle output for SVG icon component; matches all other icons in this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package with no provenance history; consistent with its publishing pattern. | ai |
Versions (showing 80 of 180)
| Version | Deps | Published |
|---|---|---|
| 3.24.4 | 4 / 3 | |
| 3.24.3 | 4 / 3 | |
| 3.24.2 | 4 / 3 | |
| 3.24.1 | 4 / 3 | |
| 3.24.0 | 4 / 3 | |
| 3.23.1 | 4 / 3 | |
| 3.23.0 | 4 / 3 | |
| 3.22.0 | 4 / 3 | |
| 3.21.2 | 4 / 1 | |
| 3.20.4 | 4 / 1 | |
| 3.20.3 | 4 / 1 | |
| 3.20.2 | 4 / 1 | |
| 3.20.1 | 4 / 1 | |
| 3.20.0 | 4 / 1 | |
| 3.19.0 | 4 / 1 | |
| 3.18.1 | 4 / 1 | |
| 3.18.0 | 4 / 1 | |
| 3.17.0 | 4 / 1 | |
| 3.16.4 | 5 / 1 | |
| 3.16.3 | 5 / 1 | |
| 3.16.2 | 5 / 1 | |
| 3.16.1 | 5 / 1 | |
| 3.16.0 | 4 / 1 | |
| 3.15.0 | 3 / 1 | |
| 3.14.16 | 3 / 1 | |
| 3.14.15 | 3 / 1 | |
| 3.14.14 | 3 / 1 | |
| 3.14.13 | 3 / 1 | |
| 3.14.12 | 3 / 1 | |
| 3.14.11 | 3 / 1 | |
| 3.14.10 | 3 / 1 | |
| 3.14.9 | 3 / 1 | |
| 3.14.8 | 3 / 1 | |
| 3.14.7 | 3 / 1 | |
| 3.14.6 | 3 / 1 | |
| 3.14.4 | 3 / 1 | |
| 3.14.3 | 3 / 1 | |
| 3.14.2 | 3 / 1 | |
| 3.14.1 | 3 / 1 | |
| 3.14.0 | 3 / 1 | |
| 3.13.2 | 3 / 1 | |
| 3.13.1 | 3 / 1 | |
| 3.13.0 | 3 / 1 | |
| 3.12.1 | 3 / 1 | |
| 3.12.0 | 3 / 1 | |
| 3.11.5 | 3 / 0 | |
| 3.11.4 | 3 / 0 | |
| 3.11.3 | 3 / 0 | |
| 3.11.2 | 3 / 0 | |
| 3.11.1 | 3 / 0 | |
| 3.11.0 | 3 / 0 | |
| 3.10.8 | 3 / 0 | |
| 3.10.7 | 3 / 0 | |
| 3.10.6 | 3 / 0 | |
| 3.10.5 | 3 / 0 | |
| 3.10.4 | 3 / 0 | |
| 3.10.3 | 3 / 0 | |
| 3.10.2 | 3 / 0 | |
| 3.10.1 | 3 / 0 | |
| 3.9.1 | 3 / 0 | |
| 3.9.0 | 3 / 0 | |
| 3.8.1 | 3 / 0 | |
| 3.8.0 | 3 / 0 | |
| 3.7.0 | 3 / 0 | |
| 3.4.7 | 3 / 0 | |
| 3.4.6 | 3 / 0 | |
| 3.4.5 | 3 / 0 | |
| 3.4.4 | 3 / 0 | |
| 3.4.3 | 3 / 0 | |
| 3.4.2 | 3 / 0 | |
| 3.4.1 | 3 / 0 | |
| 3.4.0 | 3 / 0 | |
| 3.3.1 | 3 / 0 | |
| 3.3.0 | 3 / 0 | |
| 3.2.0 | 3 / 0 | |
| 3.1.4 | 3 / 0 | |
| 3.1.3 | 3 / 0 | |
| 3.1.2 | 3 / 0 | |
| 3.1.1 | 3 / 0 | |
| 3.1.0 | 3 / 0 |
v3.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.