@elliemae/ds-form-toggle
ICE MT - Dimsum - Controlled Form Toggle
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Large ICE MT monorepo; dormancy likely reflects org-level release cadence change, not account takeover. Publisher has 284 approved packages. | ai | |
| provenance | no-provenance | AI (provenance): Internal Elliemae monorepo package; provenance attestation not part of their publish workflow across all versions. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): lodash-es is declared as both a dependency and peerDependency; phantom-dep false positive for this package. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-system | AI (dependencies): Same-org monorepo sibling dep, pinned to matching version; stable pattern for this package family. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-button-v2 | AI (dependencies): Same-org monorepo sibling dep, pinned to matching version; stable pattern for this package family. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-props-helpers | AI (dependencies): Same-org monorepo sibling dep, pinned to matching version; stable pattern for this package family. | ai |
Versions (showing 30 of 130)
| Version | Deps | Published |
|---|---|---|
| 3.20.0 | 6 / 6 | |
| 3.19.0 | 6 / 6 | |
| 3.18.1 | 6 / 6 | |
| 3.18.0 | 6 / 6 | |
| 3.17.0 | 6 / 6 | |
| 3.16.4 | 7 / 6 | |
| 3.16.0 | 7 / 6 | |
| 3.15.0 | 6 / 6 | |
| 3.14.16 | 6 / 6 | |
| 3.14.15 | 6 / 6 | |
| 3.14.14 | 6 / 6 | |
| 3.14.13 | 6 / 6 | |
| 3.14.12 | 6 / 6 | |
| 3.14.11 | 6 / 6 | |
| 3.14.10 | 6 / 6 | |
| 3.14.9 | 6 / 6 | |
| 3.14.8 | 6 / 6 | |
| 3.14.7 | 6 / 6 | |
| 3.14.6 | 6 / 6 | |
| 3.14.4 | 6 / 6 | |
| 3.14.3 | 6 / 6 | |
| 3.14.2 | 6 / 6 | |
| 3.14.1 | 6 / 6 | |
| 3.14.0 | 6 / 6 | |
| 3.13.2 | 6 / 6 | |
| 3.13.1 | 6 / 6 | |
| 3.0.3 | 6 / 7 | |
| 3.0.2 | 6 / 7 | |
| 3.0.1 | 6 / 7 | |
| 3.0.0 | 6 / 7 |
v3.20.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.19.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.18.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.18.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.17.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.16.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.16.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.15.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.14.16
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.14.15
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.14.14
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.14.13
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.14.12
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.14.11
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.14.10
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.14.9
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.14.8
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.14.7
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.14.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.14.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.14.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.14.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.14.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.14.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.13.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.13.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.0.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.0.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.0.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.0.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.