@esri/arcgis-rest-request
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@esri/arcgis-rest-fetch | AI (dependencies): Sibling package from the same @esri/arcgis-rest-js monorepo, published together at matching versions via the same CI/CD pipeline with SLSA provenance. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@esri/arcgis-rest-form-data | AI (dependencies): Sibling package from the same @esri/arcgis-rest-js monorepo, published together at matching versions via the same CI/CD pipeline with SLSA provenance. Not a third-party risk. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 4.10.3 | 4 / 1 | |
| 4.10.2 | 4 / 1 | |
| 4.10.1 | 4 / 1 | |
| 4.10.0 | 4 / 1 | |
| 4.9.1 | 4 / 1 | |
| 4.9.0 | 4 / 1 | |
| 4.8.0 | 4 / 1 | |
| 4.7.3 | 4 / 1 | |
| 4.7.2 | 4 / 1 | |
| 4.7.1 | 4 / 1 | |
| 4.7.0 | 4 / 1 | |
| 4.6.0 | 4 / 1 | |
| 4.5.1 | 4 / 1 | |
| 4.5.0 | 4 / 1 | |
| 4.4.3 | 4 / 1 | |
| 4.4.2 | 4 / 1 | |
| 4.4.1 | 4 / 1 | |
| 4.4.0 | 4 / 1 | |
| 4.3.0 | 4 / 1 | |
| 4.2.3 | 4 / 1 | |
| 4.2.2 | 4 / 1 | |
| 4.2.1 | 4 / 1 | |
| 4.2.0 | 4 / 1 | |
| 4.1.4 | 4 / 1 | |
| 4.1.3 | 4 / 1 | |
| 4.1.2 | 4 / 1 | |
| 4.1.1 | 4 / 1 | |
| 4.1.0 | 4 / 1 | |
| 4.0.4 | 3 / 0 | |
| 4.0.3 | 3 / 0 | |
| 4.0.2 | 3 / 0 | |
| 4.0.1 | 3 / 0 | |
| 4.0.0 | 3 / 0 |
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.