@elliemae/ds-card-v1-detail
ICE MT - Dimsum - Card V1 Detail
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Large established monorepo with trusted publisher; missing gitHead reflects CI config change, not a risk indicator for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Large monorepo with 695 versions; batch releases after gaps are consistent with org release cadence, not takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are lodash-es and an internal @elliemae sibling package; consistent with monorepo refactor, not suspicious. | ai | |
| provenance | no-provenance | AI (provenance): Established @elliemae monorepo; no provenance is consistent across all versions of this package family. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-legacy-button-v1 | AI (phantom-deps): Same-org monorepo dep; phantom-dep false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@xstyled/system | AI (phantom-deps): Styling utility used transitively in monorepo; stable false positive for this package. | ai |
Versions (showing 13 of 113)
| Version | Deps | Published |
|---|---|---|
| 3.27.0 | 1 / 4 | |
| 3.26.0 | 10 / 4 | |
| 3.24.6 | 10 / 4 | |
| 3.24.5 | 10 / 4 | |
| 3.24.4 | 10 / 4 | |
| 3.24.3 | 10 / 4 | |
| 3.24.2 | 10 / 4 | |
| 3.24.1 | 10 / 4 | |
| 3.24.0 | 10 / 4 | |
| 3.23.1 | 10 / 5 | |
| 3.23.0 | 10 / 5 | |
| 3.22.0 | 10 / 5 | |
| 3.21.2 | 10 / 3 |
v3.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.