← Home

@elliemae/ds-chat

ICE MT - Dimsum - Chat

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): High-volume @elliemae monorepo; missing gitHead is a CI environment change, not a supply-chain indicator for this org. ai
provenance no-provenance AI (provenance): Large internal design-system monorepo; provenance attestation not historically used by this publisher. ai

Versions (showing 51 of 186)

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

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.