← Home

@elliemae/ds-card

ICE MT - Dimsum - Card

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 monorepo package from established ICE MT publisher; missing gitHead is a minor CI environment change, not a supply-chain indicator. ai
publish-pattern dormant-publish AI (publish-pattern): Large Elliemae DS monorepo with many packages; irregular publish cadence is expected for individual sub-packages. ai
provenance no-provenance AI (provenance): Long-established ICE/Ellie Mae monorepo package; lack of provenance is consistent across all versions. ai

Versions (showing 51 of 174)

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