@things-factory/integration-label-studio
Integration module for embedding Label Studio in Things-Factory with SSO support
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:toplevel-fetch | AI (semgrep): Fetch targets same-origin SSO config endpoint; consistent with documented Label Studio SSO integration purpose. | ai | |
| phantom-deps | phantom-dep:@operato/layout | AI (phantom-deps): Same-org monorepo dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/menu-base | AI (phantom-deps): Same-org scope; declared for plugin registration, not direct import. Stable FP. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 8 / 0 | |
| 9.2.23 | 8 / 0 | |
| 9.2.22 | 8 / 0 | |
| 9.2.21 | 8 / 0 | |
| 9.2.19 | 8 / 0 | |
| 9.2.16 | 8 / 0 | |
| 9.2.13 | 8 / 0 | |
| 9.2.5 | 8 / 0 | |
| 9.1.19 | 8 / 0 |
v9.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.