@everymatrix/helper-date-navigator
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/esm/helper-date-navigator-4f3c3c05.js | AI (source-diff): Standard minified Stencil/Vaadin bundle; long lines are SVG data and bundler output, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/cjs/helper-date-navigator-ad70f19b.js | AI (source-diff): CJS variant; same legitimate Vaadin/Stencil component patterns. | ai | |
| source-diff | obfuscated-file:dist/cjs/helper-date-navigator-ad70f19b.js | AI (source-diff): CJS variant of the same minified bundle; not obfuscated malware. | ai | |
| source-diff | net-exec-file:dist/helper-date-navigator/helper-date-navigator-4f3c3c05.js | AI (source-diff): Same as ESM variant; legitimate Vaadin component code. | ai | |
| source-diff | obfuscated-file:dist/helper-date-navigator/helper-date-navigator-4f3c3c05.js | AI (source-diff): Same minified Stencil bundle; long lines are expected bundler output for this component. | ai | |
| source-diff | net-exec-file:dist/esm/helper-date-navigator-4f3c3c05.js | AI (source-diff): Network/exec pattern fires on legitimate Vaadin component fetch/Promise patterns in bundled UI code. | ai | |
| source-diff | obfuscated-file:dist/esm/helper-date-navigator-28673bc8.js | AI (source-diff): Same minified Stencil/Vaadin build output pattern; false positive. | ai | |
| source-diff | obfuscated-file:dist/cjs/helper-date-navigator-2637f184.js | AI (source-diff): Standard minified Stencil/Vaadin build output; long lines are SVG path data and bundled component code. | ai | |
| source-diff | net-exec-file:dist/cjs/helper-date-navigator-2637f184.js | AI (source-diff): Network/exec pattern fires on customElements.define and Promise usage in bundled component; no actual dropper behavior. | ai | |
| source-diff | net-exec-file:dist/esm/helper-date-navigator-28673bc8.js | AI (source-diff): Same false positive pattern as CJS counterpart. | ai | |
| source-diff | obfuscated-file:dist/helper-date-navigator/helper-date-navigator-28673bc8.js | AI (source-diff): Minified Stencil bundle; long lines are legitimate bundled component code. | ai | |
| source-diff | net-exec-file:dist/helper-date-navigator/helper-date-navigator-28673bc8.js | AI (source-diff): Same false positive; customElements/Promise usage in a UI component bundle is not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/esm/helper-date-navigator-6fa6fff7.js | AI (source-diff): Same false positive as CJS counterpart. | ai | |
| source-diff | net-exec-file:dist/helper-date-navigator/helper-date-navigator-6fa6fff7.js | AI (source-diff): False positive; customElements and Promise are standard web component APIs. | ai | |
| source-diff | obfuscated-file:dist/helper-date-navigator/helper-date-navigator-6fa6fff7.js | AI (source-diff): Minified ESM bundle; long lines are legitimate bundled component code. | ai | |
| source-diff | obfuscated-file:dist/cjs/helper-date-navigator-212cbc53.js | AI (source-diff): Standard minified Stencil/Vaadin bundle; long lines are SVG path data and bundled component code, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/cjs/helper-date-navigator-212cbc53.js | AI (source-diff): Network/exec pattern matches Vaadin customElements.define and Promise usage in component bundle, not dropper malware. | ai | |
| source-diff | obfuscated-file:dist/esm/helper-date-navigator-6fa6fff7.js | AI (source-diff): Same minified Stencil/Vaadin bundle pattern; false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped enterprise package (@everymatrix) with 126 versions; sparse metadata is typical for internal component libraries. | ai |
Versions (showing 51 of 151)
| Version | Deps | Published |
|---|---|---|
| 0.8.29 | 0 / 0 | |
| 0.8.28 | 0 / 0 | |
| 0.8.27 | 0 / 0 | |
| 0.8.26 | 0 / 0 | |
| 0.8.25 | 0 / 0 | |
| 0.8.24 | 0 / 0 | |
| 0.8.23 | 0 / 0 | |
| 0.8.22 | 0 / 0 | |
| 0.8.21 | 0 / 0 | |
| 0.8.20 | 0 / 0 | |
| 0.8.19 | 0 / 0 | |
| 0.8.18 | 0 / 0 | |
| 0.8.17 | 0 / 0 | |
| 0.8.16 | 0 / 0 | |
| 0.8.15 | 0 / 0 | |
| 0.8.9 | 0 / 0 | |
| 0.8.8 | 0 / 0 | |
| 0.8.7 | 0 / 0 | |
| 0.8.6 | 0 / 0 | |
| 0.8.5 | 0 / 0 | |
| 0.8.4 | 0 / 0 | |
| 0.8.3 | 0 / 0 | |
| 0.8.2 | 0 / 0 | |
| 0.8.1 | 0 / 0 | |
| 0.8.0 | 0 / 0 | |
| 0.7.15 | 0 / 0 | |
| 0.7.14 | 0 / 0 | |
| 0.7.13 | 0 / 0 | |
| 0.7.12 | 0 / 0 | |
| 0.7.11 | 0 / 0 | |
| 0.7.10 | 0 / 0 | |
| 0.7.9 | 0 / 0 | |
| 0.7.8 | 0 / 0 | |
| 0.7.7 | 0 / 0 | |
| 0.7.6 | 0 / 0 | |
| 0.7.5 | 0 / 0 | |
| 0.7.4 | 0 / 0 | |
| 0.7.3 | 0 / 0 | |
| 0.7.2 | 0 / 0 | |
| 0.7.1 | 0 / 0 | |
| 0.7.0 | 0 / 0 | |
| 0.6.8 | 0 / 0 | |
| 0.6.7 | 0 / 0 | |
| 0.6.6 | 0 / 0 | |
| 0.6.5 | 0 / 0 | |
| 0.6.4 | 0 / 0 | |
| 0.6.3 | 0 / 0 | |
| 0.6.2 | 0 / 0 | |
| 0.6.1 | 0 / 0 | |
| 0.6.0 | 0 / 0 | |
| 0.5.2 | 0 / 0 |
v0.8.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (goe.suta) than the most recent previously approved version (adrian.pripon) on 2026-05-26, but goe.suta 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.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.