← Home

@elliemae/ds-comments

ICE MT - Dimsum - Comments

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
publish-pattern new-deps-added AI (publish-pattern): New dep is a same-org @elliemae sibling replacing a legacy variant; routine monorepo migration pattern. ai
provenance no-provenance AI (provenance): Large established monorepo; no provenance is consistent across all versions of this package family. ai
phantom-deps phantom-dep:@elliemae/ds-dropdownmenu-v2 AI (phantom-deps): Same-org scoped package in a monorepo; likely used transitively or conditionally, stable false positive. ai

Versions (showing 51 of 172)

View all versions
Version Deps Published
3.61.8 9 / 4
3.61.7 9 / 4
3.61.6 9 / 4
3.61.5 9 / 4
3.61.4 9 / 4
3.61.2 9 / 4
3.61.1 9 / 4
3.57.13 9 / 5
3.57.6 9 / 5
3.57.4 9 / 5
3.57.3 9 / 5
3.57.2 9 / 5
3.57.1 9 / 5
3.56.4 9 / 5
3.56.3 9 / 5
3.56.2 9 / 5
3.55.6 9 / 5
3.55.2 9 / 5
3.55.1 9 / 5
3.54.9 9 / 5
3.54.8 9 / 5
3.54.7 9 / 5
3.54.6 9 / 5
3.54.5 9 / 5
3.54.4 9 / 5
3.54.2 9 / 5
3.54.1 9 / 5
3.54.0 9 / 5
3.52.1 9 / 4
3.52.0 9 / 4
3.51.7 9 / 4
3.51.6 9 / 4
3.51.5 9 / 4
3.51.4 9 / 4
3.51.3 9 / 4
3.51.2 9 / 4
3.51.1 9 / 4
3.49.8 9 / 5
3.49.7 9 / 5
3.49.6 9 / 5
3.49.5 9 / 5
3.49.4 9 / 5
3.49.3 9 / 5
3.49.2 9 / 5
3.49.1 9 / 5
3.49.0 9 / 5
3.48.1 9 / 3
3.48.0 9 / 3
3.47.1 9 / 3
3.46.7 9 / 3
3.46.6 9 / 3

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.

v3.49.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.49.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.49.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.0

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.48.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.48.0

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.47.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.46.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.46.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.