@claspo/components
Claspo Base Components
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:SysChoiceButtonsComponent/SysChoiceButtonsComponent.js | AI (source-diff): Minified webpack bundle output; code is readable utility/color logic, not obfuscated malware. | ai | |
| phantom-deps | phantom-dep:@claspo/common | AI (phantom-deps): Same-org scoped dep; likely re-exported or used transitively in monorepo. | ai | |
| phantom-deps | phantom-dep:@claspo/renderer | AI (phantom-deps): Same-org scoped dep; likely re-exported or used transitively in monorepo. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 1.10.1 | 2 / 12 | |
| 1.10.0 | 2 / 12 | |
| 1.9.3 | 2 / 12 | |
| 1.9.2 | 2 / 12 | |
| 1.9.1 | 2 / 12 | |
| 1.9.0 | 2 / 12 | |
| 1.8.2 | 2 / 12 | |
| 1.8.1 | 2 / 12 | |
| 1.8.0 | 2 / 12 | |
| 1.6.3 | 2 / 11 | |
| 1.6.2 | 2 / 11 | |
| 1.6.1 | 2 / 11 | |
| 1.6.0 | 2 / 11 | |
| 1.5.1 | 2 / 11 | |
| 1.5.0 | 2 / 11 | |
| 1.4.1 | 2 / 11 | |
| 1.4.0 | 2 / 11 | |
| 1.3.1 | 2 / 11 | |
| 1.3.0 | 2 / 11 | |
| 1.2.6 | 2 / 11 | |
| 1.2.4 | 2 / 11 | |
| 1.2.3 | 2 / 11 | |
| 1.2.2 | 2 / 11 | |
| 1.2.1 | 2 / 11 | |
| 1.2.0 | 2 / 11 | |
| 1.1.35 | 2 / 11 | |
| 1.1.34 | 2 / 11 | |
| 1.1.33 | 2 / 11 | |
| 1.1.32 | 2 / 11 | |
| 1.1.31 | 2 / 11 | |
| 1.1.30 | 2 / 11 | |
| 1.1.29 | 2 / 11 | |
| 1.1.28 | 2 / 11 | |
| 1.1.27 | 2 / 11 | |
| 1.1.26 | 2 / 11 | |
| 1.1.25 | 2 / 11 | |
| 1.1.24 | 2 / 11 | |
| 1.1.23 | 2 / 11 | |
| 1.1.22 | 2 / 14 | |
| 1.1.21 | 2 / 14 | |
| 1.1.20 | 2 / 14 | |
| 1.1.19 | 2 / 14 | |
| 1.1.18 | 2 / 14 | |
| 1.1.17 | 2 / 14 | |
| 1.1.16 | 2 / 14 | |
| 1.1.15 | 2 / 14 | |
| 1.1.14 | 2 / 14 |
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.29
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.
v1.1.28
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.
v1.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.