@blueprintjs/icons
Components, fonts, icons, and css files for creating and displaying 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/cjs/generated/components/backward-ten.js | AI (source-diff): Long lines are SVG path data in compiled icon components — standard output of BlueprintJS icon build pipeline, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/cjs/generated/components/forward-ten.js | AI (source-diff): Long lines are SVG path data in compiled icon components — standard output of BlueprintJS icon build pipeline, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/esm/generated/components/curly-braces.js | AI (source-diff): Long lines are SVG path data coordinates in generated icon components, not obfuscated code. Standard pattern for @blueprintjs/icons generated files. | ai | |
| source-diff | obfuscated-file:lib/esm/generated/components/binary-number.js | AI (source-diff): Long lines are SVG path data coordinates in generated icon components, not obfuscated code. Standard pattern for @blueprintjs/icons generated files. | ai | |
| source-diff | obfuscated-file:lib/cjs/generated/components/curly-braces.js | AI (source-diff): Long lines are SVG path data coordinates in generated icon components, not obfuscated code. Standard pattern for @blueprintjs/icons generated files. | ai | |
| source-diff | obfuscated-file:lib/cjs/generated/components/binary-number.js | AI (source-diff): Long lines are SVG path data coordinates in generated icon components, not obfuscated code. Standard pattern for @blueprintjs/icons generated files. | ai | |
| source-diff | obfuscated-file:lib/esm/generated/components/aimpoints-target.js | AI (source-diff): Long lines in icon component files are SVG path data (d attribute coordinates), not obfuscation. This is expected output for a generated icon library. | ai | |
| source-diff | obfuscated-file:lib/esnext/generated/components/aimpoints-target.js | AI (source-diff): Long lines in icon component files are SVG path data (d attribute coordinates), not obfuscation. This is expected output for a generated icon library. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @blueprintjs/icons is the legitimate Palantir Blueprint icon package; Levenshtein comparison to 'cors' is a false positive with no plausible typosquat relationship. | ai | |
| source-diff | obfuscated-file:lib/cjs/generated/components/unlink.js | AI (source-diff): Long lines are SVG path coordinate data in a compiled React icon component, not obfuscation. This is the standard build output pattern for @blueprintjs/icons icon files. | ai | |
| source-diff | obfuscated-file:lib/esnext/generated/components/unlink.js | AI (source-diff): Long lines are SVG path coordinate data in a compiled React icon component, not obfuscation. This is the standard build output pattern for @blueprintjs/icons icon files. | ai | |
| source-diff | obfuscated-file:lib/esm/generated/components/unlink.js | AI (source-diff): Long lines are SVG path coordinate data in a compiled React icon component, not obfuscation. This is the standard build output pattern for @blueprintjs/icons icon files. | ai | |
| source-diff | obfuscated-file:lib/cjs/generated/components/range-ring.js | AI (source-diff): Generated CJS icon component with long SVG path data strings; this is expected output from @blueprintjs/icons' icon generation pipeline, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/cjs/generated/components/fork-end.js | AI (source-diff): Long lines are SVG path coordinate data in generated icon components — expected output of the blueprint icon build pipeline, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/esnext/generated/components/fork-end.js | AI (source-diff): Long lines are SVG path coordinate data in generated icon components — expected output of the blueprint icon build pipeline, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/esm/generated/components/fork-end.js | AI (source-diff): Long lines are SVG path coordinate data in generated icon components — expected output of the blueprint icon build pipeline, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/cjs/generated/components/pistol.js | AI (source-diff): Long lines are SVG path coordinate data in generated icon components — a standard build artifact for @blueprintjs/icons. Not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/cjs/generated/components/globe-network-add.js | AI (source-diff): Generated icon component with inline SVG path data. Long lines are SVG path strings, not obfuscation. Standard pattern for @blueprintjs/icons generated components. | ai | |
| source-diff | obfuscated-file:lib/cjs/generated/components/engagement.js | AI (source-diff): Long lines are SVG path coordinate data in compiled icon components — a structural pattern of this icon library, not obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New source files in this icon library correspond to newly added icon components; adding icons is the normal release pattern for this package. | ai | |
| source-diff | obfuscated-file:lib/esnext/generated/components/engagement.js | AI (source-diff): Long lines are SVG path coordinate data in compiled icon components — a structural pattern of this icon library, not obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Established Palantir package with long track record; lack of Sigstore provenance is a minor gap, not a security risk for this publisher. | ai | |
| source-diff | obfuscated-file:lib/esm/generated/components/engagement.js | AI (source-diff): Long lines are SVG path coordinate data in compiled icon components — a structural pattern of this icon library, not obfuscation. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 6.9.0 | 3 / 16 | |
| 6.8.0 | 3 / 15 | |
| 6.7.0 | 3 / 15 | |
| 6.6.0 | 3 / 15 | |
| 6.5.0 | 3 / 15 | |
| 6.4.0 | 3 / 15 | |
| 6.3.1 | 3 / 15 | |
| 6.0.0 | 3 / 14 | |
| 5.23.0 | 3 / 14 | |
| 5.22.0 | 3 / 14 | |
| 5.21.0 | 3 / 14 | |
| 5.20.0 | 3 / 14 | |
| 5.19.1 | 3 / 14 | |
| 5.19.0 | 3 / 14 | |
| 5.18.1 | 3 / 14 | |
| 5.17.1 | 3 / 14 | |
| 5.16.0 | 3 / 14 | |
| 5.15.1 | 3 / 14 | |
| 5.15.0 | 3 / 14 | |
| 5.14.0 | 3 / 14 | |
| 5.13.0 | 3 / 14 | |
| 5.12.0 | 3 / 14 | |
| 5.11.0 | 3 / 14 | |
| 5.10.0 | 3 / 14 | |
| 5.9.0 | 3 / 14 | |
| 5.8.0 | 3 / 14 | |
| 5.7.1 | 3 / 14 | |
| 5.5.0 | 3 / 14 | |
| 5.4.0 | 3 / 14 | |
| 5.2.1 | 3 / 14 | |
| 5.2.0 | 3 / 14 | |
| 5.1.8 | 3 / 14 | |
| 5.1.7 | 3 / 14 | |
| 5.1.6 | 3 / 14 | |
| 5.1.5 | 3 / 14 | |
| 5.1.4 | 3 / 14 | |
| 5.1.3 | 3 / 14 | |
| 5.1.2 | 3 / 14 | |
| 5.1.1 | 3 / 14 | |
| 5.1.0 | 3 / 14 | |
| 5.0.0 | 3 / 14 |
v6.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blueprintjs.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blueprintjs.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blueprintjs.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blueprintjs.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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.
v5.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.
v5.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.
v5.0.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.