@elliemae/ds-form-layout-label
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org @elliemae/ds-grid pinned to matching monorepo version; not a third-party supply-chain risk. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-grid | AI (phantom-deps): Same org scope; likely used transitively or in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xstyled/system | AI (phantom-deps): @xstyled/system is a declared runtime dep used in config/styling; phantom-dep false positive for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 3.61.5 | 3 / 5 | |
| 3.61.4 | 3 / 5 | |
| 3.61.3 | 3 / 5 | |
| 3.61.2 | 3 / 5 | |
| 3.61.1 | 3 / 5 | |
| 3.57.15 | 4 / 6 | |
| 3.57.14 | 4 / 6 | |
| 3.57.13 | 4 / 6 | |
| 3.57.4 | 4 / 6 | |
| 3.57.3 | 4 / 6 | |
| 3.57.2 | 4 / 6 | |
| 3.57.1 | 4 / 6 | |
| 3.57.0 | 4 / 6 | |
| 3.56.4 | 4 / 6 | |
| 3.56.3 | 4 / 6 | |
| 3.56.2 | 4 / 6 | |
| 3.55.6 | 4 / 6 | |
| 3.55.2 | 4 / 6 | |
| 3.55.1 | 4 / 6 | |
| 3.54.7 | 4 / 6 | |
| 3.54.6 | 4 / 6 | |
| 3.54.5 | 4 / 6 | |
| 3.54.4 | 4 / 6 | |
| 3.54.2 | 4 / 6 | |
| 3.54.1 | 4 / 6 | |
| 3.54.0 | 4 / 6 | |
| 3.52.1 | 4 / 5 | |
| 3.52.0 | 4 / 5 |
v3.61.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.61.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: encw.dev.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.61.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: encw.dev.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.56.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.56.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.56.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.55.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.55.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.55.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: encw.dev.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.52.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.