@ydtb/tk-scope-contacts
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/pages/ContactsPage.js | AI (source-diff): Compiled TypeScript/JSX output with readable imports; long lines are bundled JSX, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/client/components/view-drawer/OverviewTab.js | AI (source-diff): Same pattern: compiled TSX output, fully readable, no malicious indicators. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal scoped package; missing description is consistent with monorepo tooling, not malicious intent. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals elevate this. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): nanoid is listed as a runtime dependency; phantom-dep heuristic likely a false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.23.12 | 13 / 12 | |
| 0.23.6 | 13 / 12 | |
| 0.23.5 | 13 / 12 | |
| 0.23.1 | 13 / 12 | |
| 0.22.0 | 13 / 12 | |
| 0.21.1 | 12 / 12 | |
| 0.19.2 | 12 / 12 | |
| 0.14.27 | 12 / 12 | |
| 0.14.26 | 12 / 12 | |
| 0.14.25 | 12 / 12 | |
| 0.14.24 | 12 / 12 | |
| 0.14.23 | 12 / 12 | |
| 0.14.22 | 12 / 12 | |
| 0.14.21 | 12 / 12 | |
| 0.14.20 | 12 / 12 | |
| 0.14.19 | 12 / 12 | |
| 0.14.18 | 12 / 12 | |
| 0.14.17 | 12 / 12 | |
| 0.14.16 | 12 / 12 | |
| 0.14.13 | 12 / 12 | |
| 0.14.11 | 12 / 12 | |
| 0.14.10 | 12 / 12 | |
| 0.14.7 | 12 / 12 |
v0.23.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
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.
[Accepted risk] Package 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.