@ydtb/tk-scope-platform
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:@ydtb/tk-scope-lib | AI (phantom-deps): Same org scope; likely a transitive/peer dep in a monorepo, not a real phantom. | ai | |
| phantom-deps | phantom-dep:@ydtb/core-layer-postgres | AI (phantom-deps): Same org scope; consistent with monorepo pattern where dep is used indirectly. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.23.5 | 12 / 2 | |
| 0.22.0 | 12 / 2 | |
| 0.21.1 | 12 / 2 | |
| 0.19.2 | 11 / 2 | |
| 0.14.27 | 11 / 2 | |
| 0.14.26 | 11 / 2 | |
| 0.14.25 | 11 / 2 | |
| 0.14.24 | 11 / 2 | |
| 0.14.23 | 11 / 2 | |
| 0.14.22 | 11 / 2 | |
| 0.14.21 | 11 / 2 | |
| 0.14.20 | 11 / 2 | |
| 0.14.19 | 11 / 2 | |
| 0.14.18 | 11 / 2 | |
| 0.14.17 | 11 / 2 | |
| 0.14.16 | 11 / 2 | |
| 0.14.13 | 11 / 2 | |
| 0.14.11 | 11 / 2 | |
| 0.14.10 | 11 / 2 | |
| 0.14.7 | 11 / 2 |
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.