@gltf-transform/functions
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with 153 versions; no provenance is consistent with its history. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 4.4.2 | 6 / 0 | |
| 4.4.1 | 6 / 0 | |
| 4.4.0 | 6 / 0 | |
| 4.3.0 | 6 / 0 | |
| 4.2.1 | 6 / 0 | |
| 4.2.0 | 6 / 0 | |
| 4.1.4 | 6 / 0 | |
| 4.1.3 | 6 / 0 | |
| 4.1.2 | 6 / 0 | |
| 4.1.1 | 6 / 0 | |
| 4.1.0 | 6 / 0 | |
| 4.0.10 | 6 / 0 | |
| 4.0.9 | 6 / 0 | |
| 4.0.8 | 6 / 0 | |
| 4.0.7 | 6 / 0 | |
| 4.0.4 | 6 / 0 | |
| 4.0.2 | 6 / 0 | |
| 4.0.1 | 6 / 0 | |
| 4.0.0 | 6 / 0 |
v4.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.