@elliemae/ds-legacy-datagrids
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@elliemae/ds-legacy-popper | AI (dependencies): Same-org sibling package in a known design system monorepo; not a security risk. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-legacy-toolbar | AI (dependencies): Same-org sibling package in a known design system monorepo; not a security risk. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-legacy-filterbar | AI (dependencies): Same-org sibling package in a known design system monorepo; not a security risk. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-legacy-dropdownmenu | AI (dependencies): Same-org sibling package in a known design system monorepo; not a security risk. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-legacy-controlled-form | AI (dependencies): Same-org sibling package in a known design system monorepo; not a security risk. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-legacy-truncated-tooltip-text | AI (dependencies): Same-org sibling package in a known design system monorepo; not a security risk. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-legacy-toolbar | AI (phantom-deps): Same-org sibling; phantom-dep heuristic false positive for monorepo packages. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating widespread provenance adoption; no other risk signals. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.0.25 | 31 / 3 | |
| 1.0.24 | 31 / 3 | |
| 1.0.23 | 31 / 3 | |
| 1.0.22 | 31 / 3 | |
| 1.0.21 | 31 / 3 | |
| 1.0.20 | 31 / 3 | |
| 1.0.17 | 31 / 3 | |
| 1.0.16 | 31 / 3 | |
| 1.0.13 | 31 / 3 | |
| 1.0.12 | 31 / 3 | |
| 1.0.11 | 31 / 3 | |
| 1.0.10 | 31 / 3 | |
| 1.0.9 | 31 / 3 | |
| 1.0.8 | 31 / 3 | |
| 1.0.7 | 31 / 3 |
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.