← Home

@esri/arcgis-rest-feature-service

11
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

patrickarlttomwaysondbouwmanajturnermjuniperrweber.esri

Keywords

ES6arcgisesrifetchpromisetypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 11 of 11)

Version Deps Published
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

v4.10.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.