← Home

@elliemae/ds-progress-indicator

ICE MT - Dimsum - Progress Indicator

51
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

encw.dev

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Package is a back-published older version from a large monorepo; missing gitHead is expected for backport/re-publish scenarios. ai
provenance no-provenance AI (provenance): Large established ICE MT monorepo; provenance absence is consistent across all versions and not a risk indicator here. ai

Versions (showing 51 of 187)

View all versions
Version Deps Published
3.61.8 3 / 3
3.61.7 3 / 3
3.61.6 3 / 3
3.61.5 3 / 3
3.61.4 3 / 3
3.61.2 3 / 3
3.61.1 3 / 3
3.57.15 3 / 4
3.57.14 3 / 4
3.57.13 3 / 4
3.57.10 3 / 4
3.57.9 3 / 4
3.57.8 3 / 4
3.57.7 3 / 4
3.57.6 3 / 4
3.57.5 3 / 4
3.57.4 3 / 4
3.57.3 3 / 4
3.57.2 3 / 4
3.57.1 3 / 4
3.57.0 3 / 4
3.56.4 4 / 4
3.56.3 4 / 4
3.56.2 4 / 4
3.55.6 4 / 4
3.55.2 4 / 4
3.55.1 4 / 4
3.54.10 4 / 4
3.54.9 4 / 4
3.54.8 4 / 4
3.54.7 4 / 4
3.54.6 4 / 4
3.54.5 4 / 4
3.54.4 4 / 4
3.54.2 4 / 4
3.54.1 4 / 4
3.54.0 4 / 4
3.52.1 4 / 4
3.52.0 4 / 4
3.51.7 4 / 4
3.51.6 4 / 4
3.51.5 4 / 4
3.51.4 4 / 4
3.51.3 4 / 4
3.51.2 4 / 4
3.51.1 4 / 4
3.49.8 4 / 5
3.49.7 4 / 5
3.49.6 4 / 5
3.49.5 4 / 5
3.49.4 4 / 5

v3.61.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.51.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.51.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.51.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.51.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.51.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.51.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.51.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.49.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.49.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.49.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.49.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.49.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.