@elliemae/ds-dropzone
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 org monorepo with consistent publish history; single missing gitHead in one version is low risk given unchanged content and strong publisher track record. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-button | AI (phantom-deps): Same-org monorepo component; phantom-dep heuristic unreliable for intra-monorepo deps. | ai | |
| phantom-deps | phantom-dep:@xstyled/styled-components | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Large enterprise monorepo; no provenance is consistent across all 638 versions of this package family. | ai |
Versions (showing 12 of 112)
| Version | Deps | Published |
|---|---|---|
| 3.27.0 | 10 / 5 | |
| 3.26.0 | 10 / 5 | |
| 3.24.6 | 11 / 5 | |
| 3.24.5 | 11 / 5 | |
| 3.24.4 | 11 / 5 | |
| 3.24.3 | 11 / 5 | |
| 3.24.2 | 11 / 5 | |
| 3.24.1 | 11 / 5 | |
| 3.24.0 | 11 / 5 | |
| 3.23.1 | 11 / 5 | |
| 3.23.0 | 11 / 5 | |
| 3.22.0 | 11 / 5 |
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.