@duetds/icons
This package includes Duet Design System Icons and related utilities.
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 | obfuscated-file:lib/assets/e-invoice.js | AI (source-diff): Long line is SVG path data in an icon asset, not obfuscated code. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Stale publisher change (498d), trusted publisher track record, no behavioral change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with legitimate handoff, not takeover, per provenance timing. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable publish (498d) rules out takeover pattern. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher lahitapiola matches the package's author org (LocalTapiola); consistent with internal account migration. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Established scoped design-system icons package; Levenshtein match to 'cors' is coincidental and not a typosquat. | ai |
Versions (showing 84 of 84)
| Version | Deps | Published |
|---|---|---|
| 4.3.6 | 0 / 8 | |
| 4.3.5 | 0 / 8 | |
| 4.3.4 | 0 / 8 | |
| 4.3.3 | 0 / 8 | |
| 4.3.2 | 0 / 8 | |
| 4.3.1 | 0 / 8 | |
| 4.3.0 | 0 / 8 | |
| 4.2.14 | 0 / 8 | |
| 4.2.13 | 0 / 8 | |
| 4.2.12 | 0 / 8 | |
| 4.2.11 | 0 / 8 | |
| 4.2.10 | 0 / 8 | |
| 4.2.9 | 0 / 8 | |
| 4.2.8 | 0 / 8 | |
| 4.2.7 | 0 / 8 | |
| 4.2.6 | 0 / 8 | |
| 4.2.5 | 0 / 8 | |
| 4.2.4 | 0 / 8 | |
| 4.2.3 | 0 / 8 | |
| 4.2.2 | 0 / 8 | |
| 4.2.1 | 0 / 8 | |
| 4.2.0 | 0 / 8 | |
| 4.1.23 | 0 / 8 | |
| 4.1.22 | 0 / 8 | |
| 4.1.21 | 0 / 8 | |
| 4.1.20 | 0 / 8 | |
| 4.1.19 | 0 / 8 | |
| 4.1.18 | 0 / 8 | |
| 4.1.17 | 0 / 8 | |
| 4.1.16 | 0 / 8 | |
| 4.1.15 | 0 / 8 | |
| 4.1.14 | 0 / 8 | |
| 4.1.13 | 0 / 8 | |
| 4.1.12 | 0 / 8 | |
| 4.1.11 | 0 / 8 | |
| 4.1.10 | 0 / 8 | |
| 4.1.9 | 0 / 8 | |
| 4.1.8 | 0 / 8 | |
| 4.1.7 | 0 / 8 | |
| 4.1.6 | 0 / 8 | |
| 4.1.5 | 0 / 8 | |
| 4.1.4 | 0 / 8 | |
| 4.1.3 | 0 / 8 | |
| 4.1.2 | 0 / 8 | |
| 4.1.1 | 0 / 8 | |
| 4.1.0 | 0 / 8 | |
| 4.0.74 | 0 / 8 | |
| 4.0.73 | 0 / 8 | |
| 4.0.72 | 0 / 8 | |
| 4.0.71 | 0 / 8 | |
| 4.0.70 | 0 / 8 | |
| 4.0.69 | 0 / 8 | |
| 4.0.68 | 0 / 8 | |
| 4.0.67 | 0 / 8 | |
| 4.0.66 | 0 / 8 | |
| 4.0.65 | 0 / 8 | |
| 4.0.64 | 0 / 8 | |
| 4.0.63 | 0 / 8 | |
| 4.0.62 | 0 / 8 | |
| 4.0.61 | 0 / 8 | |
| 4.0.60 | 0 / 8 | |
| 4.0.59 | 0 / 8 | |
| 4.0.58 | 0 / 8 | |
| 4.0.57 | 0 / 8 | |
| 4.0.56 | 0 / 8 | |
| 4.0.55 | 0 / 8 | |
| 4.0.54 | 0 / 8 | |
| 4.0.53 | 0 / 8 | |
| 4.0.52 | 0 / 8 | |
| 4.0.51 | 0 / 8 | |
| 4.0.50 | 0 / 9 | |
| 4.0.49 | 0 / 9 | |
| 4.0.48 | 0 / 9 | |
| 4.0.47 | 0 / 9 | |
| 4.0.46 | 0 / 9 | |
| 4.0.45 | 0 / 9 | |
| 4.0.44 | 0 / 9 | |
| 4.0.43 | 0 / 9 | |
| 4.0.42 | 0 / 9 | |
| 4.0.41 | 0 / 9 | |
| 4.0.40 | 0 / 9 | |
| 4.0.39 | 0 / 9 | |
| 4.0.38 | 0 / 10 | |
| 4.0.37 | 0 / 10 |
v4.3.6
3 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.
This version was published by a different npm account (lahitapiola) than the most recent previously approved version (kasimir-dka) on 2026-07-01, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.3.5
3 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.
This version was published by a different npm account (lahitapiola) than the most recent previously approved version (kasimir-dka) on 2026-06-29, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.72
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-04-30, but kasimir-dka is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.70
2 findingsThis version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-03-31. It has since remained available on npm for 473 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.68
2 findingsThis version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-03-13. It has since remained available on npm for 491 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.67
2 findingsThis version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-03-06. It has since remained available on npm for 498 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.66
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2025-02-20, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.65
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2025-02-05, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.63
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2025-01-20, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.62
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gibasm) than the most recent previously approved version (lahitapiola) on 2025-01-16, but gibasm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.55
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gibasm) than the most recent previously approved version (lahitapiola) on 2024-11-05, but gibasm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.53
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gibasm) than the most recent previously approved version (lahitapiola) on 2024-10-21, but gibasm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.46
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2024-06-24, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.44
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gibasm) than the most recent previously approved version (lahitapiola) on 2024-06-06, but gibasm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.42
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2024-06-03, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.