@elliemae/ds-card-v1
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@elliemae/ds-truncated-tooltip-text | AI (phantom-deps): Monorepo design-system pattern; same-org transitive re-exports are stable. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-separator | AI (phantom-deps): Monorepo design-system pattern; same-org transitive re-exports are stable. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-system | AI (phantom-deps): Monorepo design-system pattern; same-org transitive re-exports are stable. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-form | AI (phantom-deps): Monorepo design-system pattern; same-org transitive re-exports are stable. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-grid | AI (phantom-deps): Monorepo design-system pattern; same-org transitive re-exports are stable. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-icons | AI (phantom-deps): Monorepo design-system pattern; same-org transitive re-exports are stable. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-button | AI (phantom-deps): Monorepo design-system pattern; same-org transitive re-exports are stable. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-header | AI (phantom-deps): Monorepo design-system pattern; same-org transitive re-exports are stable. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-props-helpers | AI (dependencies): Same-monorepo sibling dep pinned to matching version; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-classnames | AI (dependencies): Same-monorepo sibling dep pinned to matching version; stable false positive for this package. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 3.61.7 | 2 / 4 | |
| 3.61.6 | 2 / 4 | |
| 3.61.5 | 2 / 4 | |
| 3.61.4 | 2 / 4 | |
| 3.61.3 | 2 / 4 | |
| 3.61.2 | 2 / 4 | |
| 3.61.1 | 2 / 4 | |
| 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 / 4 | |
| 3.52.0 | 10 / 4 |
v3.61.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.61.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.61.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.61.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.61.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.56.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.56.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.56.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.55.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.55.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.55.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.54.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.54.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.54.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.54.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.54.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.54.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.52.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.