← Home

@eqproject/eqp-dashboard

Dynamic dashboard - Angular Material based

2
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

eqpa.cipollone

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established Angular component library; lack of provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:bootstrap AI (phantom-deps): Bootstrap referenced in config/styles, not directly imported in TS; expected pattern for Angular UI libs. ai
phantom-deps phantom-dep:@ngx-translate/core AI (phantom-deps): Peer/config-level dependency for i18n; not directly imported in source is normal for Angular module deps. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dep; stable false positive for Angular libraries. ai
phantom-deps phantom-dep:resize-observer-polyfill AI (phantom-deps): Polyfill referenced in config, not imported directly; stable false positive. ai
phantom-deps phantom-dep:@ngx-translate/http-loader AI (phantom-deps): Config-level i18n loader; not directly imported in TS is expected for Angular module setup. ai
phantom-deps phantom-dep:@juggle/resize-observer AI (phantom-deps): Polyfill referenced in config, not imported directly; stable false positive. ai

Versions (showing 2 of 2)

Version Deps Published
21.0.0 11 / 0
3.0.5 11 / 0

v21.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.