@things-factory/tutorial-ui
UI module for handling app tutorial usage
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@things-factory/shell | AI (dependencies): Same-org sibling package in the things-factory monorepo; consistent pattern across all versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org @things-factory scope, replacing a similar layout dep; not an external supply-chain risk. | ai | |
| provenance | no-provenance | AI (provenance): Large monorepo with 945 versions; no provenance is consistent across all releases for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/i18n-base | AI (phantom-deps): Same-org dependency declared for transitive/peer use; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/tutorial-base | AI (phantom-deps): Same-org dependency declared for transitive/peer use; stable false positive for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 5 / 0 | |
| 9.2.19 | 5 / 0 | |
| 9.2.17 | 5 / 0 | |
| 9.1.0 | 5 / 0 | |
| 9.0.41 | 5 / 0 | |
| 9.0.34 | 5 / 0 | |
| 9.0.24 | 5 / 0 | |
| 8.0.88 | 5 / 0 | |
| 8.0.87 | 5 / 0 | |
| 8.0.63 | 5 / 0 | |
| 6.4.10 | 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.695 | 5 / 0 | |
| 4.3.689 | 5 / 0 |
v9.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.63
2 findingsThis version was published by a different npm account than previous versions on 2025-11-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.10
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.764
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.755
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.752
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.743
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.740
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.738
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.695
2 findingsThis version was published by a different npm account than previous versions on 2025-11-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.689
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.