@esri/arcgis-rest-feature-service
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:pbf | AI (dependencies): pbf is a well-known Protocol Buffer library commonly used in GIS/mapping contexts; its use in an Esri feature service package is expected and legitimate. | ai | |
| dependencies | unvetted-peer-dep:@esri/arcgis-rest-request | AI (dependencies): Sibling package in the same Esri arcgis-rest-js monorepo; not an independent third-party dependency risk. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.10.3 | 2 / 2 | |
| 4.10.2 | 2 / 2 | |
| 4.10.1 | 2 / 2 | |
| 4.10.0 | 2 / 2 | |
| 4.9.1 | 2 / 2 | |
| 4.9.0 | 1 / 2 | |
| 4.8.0 | 1 / 2 | |
| 4.4.1 | 1 / 2 | |
| 4.4.0 | 1 / 2 | |
| 4.3.0 | 1 / 2 | |
| 4.2.0 | 1 / 2 | |
| 4.1.1 | 1 / 2 | |
| 4.1.0 | 1 / 2 | |
| 4.0.6 | 1 / 2 | |
| 4.0.5 | 1 / 2 | |
| 4.0.4 | 1 / 2 | |
| 4.0.3 | 1 / 2 | |
| 4.0.2 | 1 / 2 | |
| 4.0.1 | 1 / 2 | |
| 4.0.0 | 1 / 2 |
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
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.