← Home

@arcgis/languages-api-utils

npm Homepage

ArcGIS Languages API Utilities

23
Versions
SEE LICENSE IN LICENSE.md
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

odoeffaubrydpaddockdan11669twesterhuys

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit runtime dependency for TypeScript-compiled packages; stable false positive. ai
bogus-package bogus-package AI (bogus-package): ArcGIS SDK utility package; sparse README and no keywords are normal for internal SDK components. ai

Versions (showing 23 of 23)

Version Deps Published
5.1.14 3 / 0
5.1.13 3 / 0
5.1.12 3 / 0
5.1.11 3 / 0
5.1.10 3 / 0
5.1.9 3 / 0
5.1.8 3 / 0
5.1.7 3 / 0
5.1.6 3 / 0
5.1.5 3 / 0
5.1.4 3 / 0
5.1.3 3 / 0
5.1.2 3 / 0
5.1.1 3 / 0
5.1.0 3 / 0
5.0.19 3 / 0
5.0.18 3 / 0
5.0.17 3 / 0
5.0.16 3 / 0
4.34.9 3 / 0
4.34.8 3 / 0
4.34.7 3 / 0
4.32.16 3 / 0

v5.1.14

1 finding
LOW No provenance attestation provenance

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

v5.1.13

1 finding
LOW No provenance attestation provenance

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

v5.1.12

1 finding
LOW No provenance attestation provenance

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

v5.1.11

1 finding
LOW No provenance attestation provenance

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

v5.1.10

1 finding
LOW No provenance attestation provenance

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

v5.1.9

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dan11669.

LOW No provenance attestation provenance

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

v5.1.8

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dan11669.

LOW No provenance attestation provenance

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

v5.1.7

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dan11669.

LOW No provenance attestation provenance

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

v4.34.9

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ffaubry → dan11669 (on 2025-11-06, known maintainer) provenance

This version was published by a different npm account (dan11669) than the most recent previously approved version (ffaubry) on 2025-11-06, but dan11669 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.