@ydtb/tk-scope-team
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/src/client/components/CreateBotDialog.js | AI (source-diff): Standard tsc-compiled ESM output; long lines from import lists, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/src/client/components/member/MemberApiKeysTab.js | AI (source-diff): Standard tsc-compiled ESM output; long lines from import lists, not obfuscation. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@ydtb/tk-scope-auth | AI (phantom-deps): Same-org monorepo dep; declared but may be used transitively or via re-exports. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@ydtb/tk-scope-platform | AI (phantom-deps): Same-org monorepo dep; declared as runtime dependency, phantom-dep heuristic is a false positive here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.23.6 | 12 / 11 | |
| 0.23.5 | 12 / 11 | |
| 0.22.0 | 11 / 12 | |
| 0.21.1 | 11 / 12 | |
| 0.19.2 | 11 / 12 | |
| 0.14.27 | 11 / 12 | |
| 0.14.26 | 11 / 12 | |
| 0.14.25 | 11 / 12 | |
| 0.14.24 | 11 / 12 | |
| 0.14.23 | 11 / 12 | |
| 0.14.22 | 11 / 12 | |
| 0.14.21 | 11 / 12 | |
| 0.14.20 | 11 / 12 | |
| 0.14.19 | 11 / 12 | |
| 0.14.18 | 11 / 12 | |
| 0.14.17 | 11 / 12 | |
| 0.14.16 | 11 / 12 | |
| 0.14.13 | 11 / 12 | |
| 0.14.11 | 11 / 12 | |
| 0.14.10 | 11 / 12 | |
| 0.14.7 | 11 / 12 |
v0.23.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.5
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.