@elliemae/ds-card-v2 MIT 27 versions

@elliemae/ds-card-v2

npm Repository

ICE MT - Dimsum - Card V2

27

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

encw.dev

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:lodash-es	AI (phantom-deps): lodash-es is declared as both a dep and peerDep; phantom-dep heuristic false positive for this monorepo package.	ai	2026/05/16
phantom-deps	phantom-dep:@elliemae/ds-icons	AI (phantom-deps): Same-org monorepo component; phantom-dep heuristic fires routinely across this package family.	ai	2026/05/16
phantom-deps	phantom-dep:@elliemae/ds-button	AI (phantom-deps): Same-org monorepo component; stable false positive for this package.	ai	2026/05/16
phantom-deps	phantom-dep:@elliemae/ds-separator	AI (phantom-deps): Same-org monorepo component; stable false positive for this package.	ai	2026/05/16
phantom-deps	phantom-dep:@elliemae/ds-controlled-form	AI (phantom-deps): Same-org monorepo component; stable false positive for this package.	ai	2026/05/16
phantom-deps	phantom-dep:@elliemae/ds-legacy-header	AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic fires as false positive for this monorepo package.	ai	2026/04/29

Versions (showing 27 of 27)

Version	Deps	Published
3.61.5	6 / 5	2026-06-04
3.61.4	6 / 5	2026-05-04
3.61.2	6 / 5	2026-04-27
3.61.1	6 / 5	2026-04-27
3.57.14	7 / 7	2026-05-22
3.57.13	7 / 7	2026-05-20
3.57.4	7 / 7	2026-01-12
3.57.3	7 / 7	2026-01-06
3.57.2	7 / 7	2026-01-06
3.57.1	7 / 7	2026-01-05
3.57.0	7 / 7	2026-01-05
3.56.4	11 / 6	2025-11-04
3.56.3	11 / 6	2025-11-03
3.56.2	11 / 6	2025-11-03
3.55.6	11 / 6	2025-11-18
3.55.2	11 / 6	2025-10-21
3.55.1	11 / 6	2025-10-09
3.54.8	11 / 6	2026-01-08
3.54.7	11 / 6	2025-11-26
3.54.6	11 / 6	2025-11-20
3.54.5	11 / 6	2025-11-05
3.54.4	11 / 6	2025-10-13
3.54.2	11 / 6	2025-09-24
3.54.1	11 / 6	2025-08-19
3.54.0	11 / 6	2025-08-18
3.52.1	11 / 5	2025-05-26
3.52.0	11 / 5	2025-05-23

v3.61.5

1 finding

LOW No provenance attestation provenance

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

v3.61.4

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: encw.dev.

LOW No provenance attestation provenance

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

v3.61.1

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.57.14

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: encw.dev.

LOW No provenance attestation provenance

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

v3.57.13

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: encw.dev.

LOW No provenance attestation provenance

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

v3.57.4

1 finding

LOW No provenance attestation provenance

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

v3.57.3

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.57.2

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.57.1

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.57.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.56.4

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.56.3

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.56.2

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.55.6

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.55.2

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.55.1

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.54.8

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.54.7

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.54.6

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.54.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.

v3.54.4

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.54.2

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.54.1

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.54.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.52.1

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.52.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.