@things-factory/routing-base
Server module that handles Routing
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/auth-base | AI (dependencies): Same-org sibling dependency in the things-factory monorepo; consistently co-versioned across releases. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires in a migrations file-loader that resolves local migration files; not user-controlled input. | ai | |
| provenance | no-provenance | AI (provenance): Long-lived monorepo package; provenance absence is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 3 / 0 | |
| 9.2.19 | 3 / 0 | |
| 9.1.0 | 3 / 0 | |
| 9.0.41 | 3 / 0 | |
| 9.0.36 | 3 / 0 | |
| 9.0.34 | 3 / 0 | |
| 9.0.25 | 3 / 0 | |
| 9.0.5 | 3 / 0 | |
| 9.0.2 | 3 / 0 | |
| 8.0.88 | 3 / 0 | |
| 8.0.87 | 3 / 0 | |
| 8.0.63 | 3 / 0 | |
| 4.3.734 | 3 / 0 | |
| 4.3.689 | 3 / 0 |
v9.2.24
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. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
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 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.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.734
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.689
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.