@ydtb/tk-scope-integrations
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:@orpc/server | AI (dependencies): @orpc/server is a legitimate RPC framework; its use in an integration library is expected. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo package; missing description is consistent with private/org tooling pattern. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.23.5 | 8 / 4 | |
| 0.22.0 | 8 / 4 | |
| 0.21.1 | 8 / 4 | |
| 0.19.2 | 8 / 4 | |
| 0.14.27 | 8 / 4 | |
| 0.14.26 | 8 / 4 | |
| 0.14.25 | 8 / 4 | |
| 0.14.24 | 8 / 4 | |
| 0.14.23 | 8 / 4 | |
| 0.14.22 | 8 / 4 | |
| 0.14.21 | 8 / 4 | |
| 0.14.20 | 8 / 4 | |
| 0.14.19 | 8 / 4 | |
| 0.14.18 | 8 / 4 | |
| 0.14.17 | 8 / 4 | |
| 0.14.16 | 8 / 4 | |
| 0.14.13 | 8 / 4 | |
| 0.14.11 | 6 / 4 | |
| 0.14.10 | 6 / 4 | |
| 0.14.7 | 6 / 4 |
v0.23.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.