@semcore/time-picker
Semrush TimePicker Component
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:lib/cjs/TimePicker.js | AI (source-diff): Babel-compiled output with inlined minified CSS; standard build artifact for @semcore packages. | ai | |
| source-diff | obfuscated-file:lib/es6/TimePicker.js | AI (source-diff): Same as above — Babel ES6 build output with inlined CSS, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/esm/TimePicker.mjs | AI (source-diff): Same as above — ESM build output with inlined CSS, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@semcore/button | AI (phantom-deps): Same-org @semcore scope; declared as dep, phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 17.2.0 | 3 / 3 | |
| 17.1.0 | 3 / 3 | |
| 17.0.1 | 3 / 3 | |
| 17.0.0 | 3 / 3 | |
| 16.2.1 | 4 / 2 | |
| 16.2.0 | 4 / 2 | |
| 16.1.13 | 4 / 2 | |
| 16.1.12 | 4 / 2 | |
| 4.53.0 | 5 / 2 |
v17.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.1
4 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.
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.
v16.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.53.0
5 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.
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.
This version was published by a different npm account (semrushinc) than the most recent previously approved version (uikit-team) on 2026-05-13, but semrushinc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.