@elliemae/ds-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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): High-volume monorepo publisher with clean track record; missing gitHead reflects CI environment change, not a supply-chain risk. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Large ICE MT monorepo with many back-published patch versions; pattern is consistent with org release practices. | ai | |
| provenance | no-provenance | AI (provenance): Established internal ICE MT/Elliemae package; provenance not used across this package family. | ai |
Versions (showing 81 of 81)
| Version | Deps | Published |
|---|---|---|
| 3.57.15 | 1 / 4 | |
| 3.57.14 | 1 / 4 | |
| 3.57.13 | 1 / 4 | |
| 3.57.10 | 1 / 4 | |
| 3.57.9 | 1 / 4 | |
| 3.57.8 | 1 / 4 | |
| 3.57.7 | 1 / 4 | |
| 3.57.6 | 1 / 4 | |
| 3.57.5 | 1 / 4 | |
| 3.57.4 | 1 / 4 | |
| 3.57.3 | 1 / 4 | |
| 3.57.2 | 1 / 4 | |
| 3.57.1 | 1 / 4 | |
| 3.57.0 | 1 / 4 | |
| 3.56.4 | 1 / 4 | |
| 3.56.3 | 1 / 4 | |
| 3.56.2 | 1 / 4 | |
| 3.55.6 | 1 / 4 | |
| 3.55.2 | 1 / 4 | |
| 3.55.1 | 1 / 4 | |
| 3.54.10 | 1 / 4 | |
| 3.54.9 | 1 / 4 | |
| 3.54.8 | 1 / 4 | |
| 3.54.7 | 1 / 4 | |
| 3.54.6 | 1 / 4 | |
| 3.54.5 | 1 / 4 | |
| 3.54.4 | 1 / 4 | |
| 3.54.3 | 1 / 4 | |
| 3.54.2 | 1 / 4 | |
| 3.54.1 | 1 / 4 | |
| 3.54.0 | 1 / 4 | |
| 3.52.1 | 1 / 4 | |
| 3.52.0 | 1 / 4 | |
| 3.51.7 | 1 / 4 | |
| 3.51.6 | 1 / 4 | |
| 3.51.5 | 1 / 4 | |
| 3.51.4 | 1 / 4 | |
| 3.51.3 | 1 / 4 | |
| 3.51.2 | 1 / 4 | |
| 3.51.1 | 1 / 4 | |
| 3.51.0 | 1 / 4 | |
| 3.49.8 | 1 / 5 | |
| 3.49.7 | 1 / 5 | |
| 3.49.6 | 1 / 5 | |
| 3.49.5 | 1 / 5 | |
| 3.49.4 | 1 / 5 | |
| 3.49.3 | 1 / 5 | |
| 3.49.2 | 1 / 5 | |
| 3.49.1 | 1 / 5 | |
| 3.49.0 | 1 / 5 | |
| 3.48.1 | 1 / 3 | |
| 3.48.0 | 1 / 3 | |
| 3.47.1 | 1 / 3 | |
| 3.46.7 | 1 / 3 | |
| 3.46.6 | 1 / 3 | |
| 3.46.5 | 1 / 3 | |
| 3.46.4 | 1 / 3 | |
| 3.46.3 | 1 / 3 | |
| 3.46.2 | 1 / 3 | |
| 3.46.1 | 1 / 3 | |
| 3.46.0 | 1 / 3 | |
| 3.45.1 | 1 / 3 | |
| 3.45.0 | 1 / 3 | |
| 3.42.0 | 1 / 3 | |
| 3.41.1 | 1 / 3 | |
| 3.41.0 | 1 / 3 | |
| 3.40.0 | 1 / 3 | |
| 3.39.6 | 1 / 3 | |
| 3.39.5 | 1 / 3 | |
| 3.39.4 | 1 / 3 | |
| 3.39.3 | 1 / 3 | |
| 3.39.2 | 1 / 3 | |
| 3.39.1 | 1 / 3 | |
| 3.39.0 | 1 / 3 | |
| 3.38.0 | 1 / 3 | |
| 3.37.3 | 1 / 3 | |
| 3.37.2 | 1 / 3 | |
| 3.37.1 | 1 / 3 | |
| 3.37.0 | 1 / 3 | |
| 3.35.0 | 1 / 3 | |
| 3.34.0 | 1 / 3 |
v3.51.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.48.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.45.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.41.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.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.39.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.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.34.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.