@ydtb/tk-scope-extension
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal org package; missing description is consistent across versions and not a malware indicator here. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is a process gap, not a security issue for this established org package. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): hono is a declared dependency used in config/server context; phantom-dep heuristic fires on indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:@ydtb/tk-scope | AI (phantom-deps): Same-org dep declared in dependencies; phantom-dep fires on indirect/re-export patterns common in monorepos. | ai | |
| phantom-deps | phantom-dep:@ydtb/tk-scope-lib | AI (phantom-deps): Same-org dep declared in dependencies; monorepo re-export pattern. | ai | |
| phantom-deps | phantom-dep:@ydtb/core-layer-postgres | AI (phantom-deps): Same-org dep declared in dependencies; monorepo re-export pattern. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.22.0 | 12 / 5 | |
| 0.21.1 | 12 / 5 | |
| 0.19.2 | 12 / 5 | |
| 0.14.27 | 12 / 5 | |
| 0.14.26 | 12 / 5 | |
| 0.14.25 | 12 / 5 | |
| 0.14.24 | 12 / 5 | |
| 0.14.23 | 12 / 5 | |
| 0.14.22 | 12 / 5 | |
| 0.14.21 | 12 / 5 | |
| 0.14.20 | 12 / 5 | |
| 0.14.19 | 12 / 5 | |
| 0.14.18 | 12 / 5 | |
| 0.14.17 | 12 / 5 | |
| 0.14.16 | 12 / 5 | |
| 0.14.13 | 12 / 5 | |
| 0.14.11 | 12 / 5 | |
| 0.14.10 | 12 / 5 | |
| 0.14.7 | 12 / 6 |
v0.22.0
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.11
1 finding[Accepted risk] Package 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.