@eqproject/eqp-datetimerangepicker
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 5 approved packages; this is a legitimate Angular 21 compatibility update after a dormancy period. | ai | |
| phantom-deps | phantom-dep:ngx-translate | AI (phantom-deps): ngx-translate is a security-placeholder package on npm; declared but not imported, stable false positive for this package. | ai | |
| dependencies | unvetted-dep:ngx-translate | AI (dependencies): [email protected] is an npm security placeholder package, not a functional dependency; real translation is via @ngx-translate/core. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known Angular implicit runtime dep; stable false positive for Angular libraries. | ai | |
| phantom-deps | phantom-dep:@ngx-translate/http-loader | AI (phantom-deps): http-loader is a companion to @ngx-translate/core; config-only reference is standard Angular i18n setup. | ai | |
| phantom-deps | phantom-dep:bootstrap | AI (phantom-deps): Bootstrap referenced in config/styles for UI theming; not a direct import pattern for Angular libs. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Popper is a peer/indirect dep of Bootstrap; config-only reference is expected. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 21.0.1 | 9 / 0 | |
| 21.0.0 | 9 / 0 | |
| 3.0.9 | 11 / 0 | |
| 3.0.8 | 11 / 0 | |
| 3.0.7 | 11 / 0 | |
| 3.0.6 | 11 / 0 |
v21.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.