@things-factory/organization
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:@operato/app | AI (phantom-deps): Same-org monorepo dep referenced in config; phantom-dep heuristic false positive for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Migration file loader pattern — requires local files resolved by path.resolve(); not arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:@things-factory/code-ui | AI (phantom-deps): Same-org scoped dep; declared in package.json, likely used indirectly or in non-imported entry points. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 10 / 0 | |
| 9.2.5 | 10 / 0 | |
| 9.1.19 | 10 / 0 | |
| 8.0.76 | 10 / 0 | |
| 8.0.63 | 10 / 0 | |
| 6.4.8 | 8 / 0 |
v9.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.63
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. Only ~12% of npm packages have provenance, so this is common but not ideal.