@tiktokshop/widget-kit-react
## Get Started
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Legitimate scoped official package with sparse metadata, not spam. | ai | |
| source-diff | obfuscated-file-transition:dist/index.cjs | AI (source-diff): Standard bundler minification, not obfuscation; no malicious payload in sample. | ai | |
| source-diff | obfuscated-file-transition:dist/index.mjs | AI (source-diff): Standard bundler minification, not obfuscation; no malicious payload in sample. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase consistent with bundled dist build output. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.4 | 1 / 19 | |
| 1.0.3 | 1 / 10 | |
| 1.0.2 | 1 / 10 | |
| 1.0.1 | 1 / 4 | |
| 1.0.0 | 1 / 4 |
v1.0.3
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.