@elliemae/ds-toolbar-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, 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): Long-established @elliemae monorepo package; missing gitHead is a CI config change, not a supply-chain indicator. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-legacy-toolbar-v1 | AI (dependencies): Sibling package in the same @elliemae org/monorepo; consistent with the package's design system context. | ai | |
| provenance | no-provenance | AI (provenance): Entire @elliemae/ds-* monorepo publishes without Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 14 of 114)
| Version | Deps | Published |
|---|---|---|
| 3.29.1 | 1 / 3 | |
| 3.29.0 | 1 / 3 | |
| 3.27.0 | 1 / 3 | |
| 3.26.0 | 7 / 3 | |
| 3.24.6 | 7 / 3 | |
| 3.24.5 | 7 / 3 | |
| 3.24.4 | 7 / 3 | |
| 3.24.3 | 7 / 3 | |
| 3.24.2 | 7 / 3 | |
| 3.24.1 | 7 / 3 | |
| 3.24.0 | 7 / 3 | |
| 3.23.1 | 7 / 6 | |
| 3.23.0 | 7 / 6 | |
| 3.22.0 | 7 / 6 |
v3.29.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.29.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.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.