← Home

@squiz/component-web-api-lib

npm
14
Versions
—
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

squiz-npm-publishcdlohpcoshansquiztadams_squizscott_ackerabarnes_squizgsherwoodpnollandchadszinow-squizdeborahsherwoodgriseboroughakareliasdanisolivernealazakensazenderowska.squizlnowakmdobiebmattersewyattadakrupalwright-sqcupretijmatthew_squizwjaroszbxwucarlfostersamortyyang1029squiz-dwebstertsmythrainger_squizajhawaruqureshithomasgrobavanschoor-squizata-squizasharpe-squizaj12squiz-lstephansquiz-ncallahansquiz-dschoensquiz-ksilalahijpolgar-squizpkiriakourmcavoy-squizjchawaremnowakowski1pantyporowicz-squizdjarrott.squiz.netdkaczmarekbgribbinsukratubhalineenanaaronchan1010haleesquizrszarafinskitmaddengdemelloesilva.squizjwrobelbpottierhkapoor_squizjhendersonsquizjoshsquizcross-squizsjamesquizdheffernantmalinowskiriddhi_17andrew-squizhadiroudakitrais.squizdcousinszzainabdawidnastevenssquiz

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Squiz org rotation; publisher is a known maintainer with clean track record. ai
maintainer-change maintainer-removed AI (maintainer-change): Squiz org rotation; no evidence of hostile takeover alongside known-maintainer publish. ai
publish-pattern dormant-publish AI (publish-pattern): 504-version established package; dormancy followed by known-maintainer publish is consistent with org workflow changes. ai

Versions (showing 14 of 14)

Version Deps Published
1.75.0 2 / 4
1.74.2 2 / 4
1.74.1 2 / 4
1.74.0 2 / 4
1.73.4 2 / 4
1.73.3 2 / 4
1.73.2 2 / 4
1.73.1 2 / 4
1.73.0 2 / 4
1.72.0 2 / 4
1.71.0 2 / 4
1.70.3 2 / 4
1.70.2 2 / 4
1.70.1 2 / 4

v1.75.0

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.

v1.74.2

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.

v1.74.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.

v1.74.0

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.

v1.73.4

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: carlfoster → jmatthew_squiz (on 2025-12-11, known maintainer) provenance

This version was published by a different npm account (jmatthew_squiz) than the most recent previously approved version (carlfoster) on 2025-12-11, but jmatthew_squiz 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.

v1.73.3

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.

v1.73.2

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: squiz-npm-publish → carlfoster (on 2025-10-29, known maintainer) provenance

This version was published by a different npm account (carlfoster) than the most recent previously approved version (squiz-npm-publish) on 2025-10-29, but carlfoster 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.

v1.73.1

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: squiz-npm-publish → carlfoster (on 2025-09-30, known maintainer) provenance

This version was published by a different npm account (carlfoster) than the most recent previously approved version (squiz-npm-publish) on 2025-09-30, but carlfoster 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.

v1.73.0

1 finding
LOW No provenance attestation provenance

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

v1.72.0

1 finding
LOW No provenance attestation provenance

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

v1.71.0

1 finding
LOW No provenance attestation provenance

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

v1.70.3

1 finding
LOW No provenance attestation provenance

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

v1.70.2

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.

v1.70.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.