@things-factory/context-ui
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@material/mwc-icon | AI (phantom-deps): Web component dependency used in client-side bundles; not directly imported in JS but legitimately declared as runtime dep. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal UI component in a large monorepo; short README and empty server entry are expected for this package type. | ai | |
| phantom-deps | phantom-dep:@things-factory/layout-ui | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on declared-but-not-directly-imported pattern common in monorepo packages. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 9.2.13 | 4 / 0 | |
| 9.2.5 | 4 / 0 | |
| 9.1.19 | 4 / 0 | |
| 8.0.86 | 4 / 0 | |
| 6.4.10 | 4 / 0 | |
| 6.4.8 | 4 / 0 | |
| 4.3.815 | 5 / 0 | |
| 4.3.767 | 5 / 0 | |
| 4.3.764 | 5 / 0 | |
| 4.3.755 | 5 / 0 | |
| 4.3.752 | 5 / 0 | |
| 4.3.743 | 5 / 0 | |
| 4.3.740 | 5 / 0 | |
| 4.3.738 | 5 / 0 | |
| 4.3.734 | 5 / 0 | |
| 4.3.729 | 5 / 0 | |
| 4.3.727 | 5 / 0 | |
| 4.3.725 | 5 / 0 | |
| 4.3.723 | 5 / 0 | |
| 4.3.705 | 5 / 0 | |
| 4.3.695 | 5 / 0 |
v9.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.815
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.767
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.764
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.755
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.752
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.743
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.740
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.738
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.734
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.729
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.727
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.725
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.723
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.705
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.695
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.