← Home

url-template

npm Repository Homepage

A URI template implementation (RFC 6570 compliant)

13
Versions
BSD-3-Clause
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

jkoopsbramstein

Keywords

uri-templateuri templateuriurlrfc 6570url templateurl-template

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): jonkoops has been the publisher since 2022; legitimate maintainer transition on a 13-year-old package with 11M+ weekly downloads. ai
maintainer-change maintainer-added AI (maintainer-change): jonkoops added as maintainer ~3 years ago; established publisher with clean track record (26 approvals, 0 rejections). ai
source-diff source-size-dropped AI (source-diff): Major version bump (v2→v3) with ESM migration; 4KB is appropriate for a single-RFC utility library. ai

Versions (showing 13 of 13)

Version Deps Published
3.1.1 0 / 2
3.1.0 0 / 2
3.0.0 0 / 2
2.0.8 0 / 2
2.0.7 0 / 2
2.0.6 0 / 2
2.0.5 0 / 2
2.0.4 0 / 2
2.0.2 0 / 2
2.0.1 0 / 2
2.0.0 0 / 2
1.1.0 0 / 2
1.0.0 0 / 2

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

2 findings
HIGH Publisher changed: bramstein → jkoops (on 2022-07-17) provenance

This version was published by a different npm account than previous versions on 2022-07-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.0.0

2 findings
HIGH Publisher changed: bramstein → jonkoops (on 2022-01-31) provenance

This version was published by a different npm account than previous versions on 2022-01-31. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.8

1 finding
LOW No provenance attestation provenance

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

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.0.6

1 finding
LOW No provenance attestation provenance

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

v2.0.5

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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