@feathersjs/transport-commons
Shared functionality for websocket providers
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:radix-router | AI (dependencies): radix-router is a legitimate URL routing library; its use in @feathersjs/transport-commons for websocket routing is expected and stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established FeathersJS monorepo package with a long history; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 5.0.46 | 5 / 8 | |
| 5.0.45 | 5 / 8 | |
| 5.0.44 | 5 / 8 | |
| 5.0.43 | 5 / 8 | |
| 5.0.42 | 5 / 8 | |
| 5.0.41 | 5 / 8 | |
| 5.0.40 | 5 / 8 | |
| 5.0.39 | 5 / 8 | |
| 5.0.37 | 5 / 8 | |
| 5.0.36 | 5 / 8 | |
| 5.0.35 | 5 / 8 | |
| 5.0.34 | 5 / 8 | |
| 5.0.33 | 5 / 8 | |
| 5.0.32 | 5 / 8 | |
| 5.0.31 | 5 / 8 | |
| 5.0.30 | 5 / 8 | |
| 5.0.29 | 5 / 8 | |
| 5.0.28 | 5 / 8 | |
| 5.0.27 | 5 / 8 | |
| 5.0.26 | 5 / 8 | |
| 5.0.25 | 5 / 8 | |
| 5.0.24 | 5 / 8 | |
| 5.0.23 | 5 / 8 | |
| 5.0.22 | 5 / 8 | |
| 5.0.21 | 5 / 8 | |
| 5.0.20 | 5 / 8 | |
| 5.0.19 | 5 / 8 | |
| 5.0.18 | 5 / 8 | |
| 5.0.17 | 5 / 8 | |
| 5.0.16 | 5 / 8 | |
| 5.0.15 | 5 / 8 | |
| 5.0.14 | 5 / 8 | |
| 5.0.13 | 5 / 8 | |
| 5.0.12 | 5 / 8 | |
| 5.0.11 | 5 / 8 | |
| 5.0.10 | 5 / 8 | |
| 5.0.9 | 5 / 8 | |
| 5.0.8 | 5 / 8 | |
| 4.5.19 | 5 / 8 |
v5.0.46
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (daffl) than the most recent previously approved version (marshallswain) on 2026-06-27, but daffl is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.