@simplybusiness/icons
Library of Simply Business 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/index.js | AI (source-diff): Standard esbuild CJS bundle for an icon library; long lines are minified SVG/export data, not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped org package @simplybusiness/icons; Levenshtein match to 'cors' is coincidental, not a typosquat. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 5.1.1 | 0 / 10 | |
| 5.1.0 | 0 / 9 | |
| 5.0.4 | 0 / 9 | |
| 5.0.3 | 0 / 11 | |
| 5.0.2 | 0 / 11 | |
| 5.0.1 | 0 / 11 | |
| 5.0.0 | 0 / 11 | |
| 4.41.0 | 0 / 11 | |
| 4.40.2 | 0 / 11 | |
| 4.40.1 | 0 / 11 | |
| 4.40.0 | 0 / 11 | |
| 4.39.0 | 0 / 9 | |
| 4.38.0 | 0 / 9 | |
| 4.37.0 | 0 / 9 | |
| 4.36.0 | 0 / 9 | |
| 4.35.0 | 0 / 9 | |
| 4.34.0 | 0 / 9 |
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
2 findingsNewly 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.
v5.0.2
2 findingsNewly 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.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.40.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.