@everymatrix/ui-image
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Auto-generated UI component in a large monorepo; missing metadata is a build artifact pattern, not spam. | ai | |
| phantom-deps | phantom-dep:@everymatrix/ui-skeleton | AI (phantom-deps): Same org scope; likely used indirectly via web component registration, stable false positive for this package family. | ai |
Versions (showing 15 of 225)
| Version | Deps | Published |
|---|---|---|
| 1.72.0 | 1 / 0 | |
| 1.71.1 | 1 / 0 | |
| 1.71.0 | 1 / 0 | |
| 1.70.1 | 1 / 0 | |
| 1.70.0 | 1 / 0 | |
| 1.69.3 | 1 / 0 | |
| 1.69.2 | 1 / 0 | |
| 1.69.0 | 1 / 0 | |
| 1.68.0 | 1 / 0 | |
| 1.67.3 | 1 / 0 | |
| 1.67.0 | 1 / 0 | |
| 1.66.2 | 1 / 0 | |
| 1.66.1 | 1 / 0 | |
| 1.66.0 | 1 / 0 | |
| 1.65.3 | 1 / 0 |
v1.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.67.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.