← Home

@squiz/dx-common-lib

npm
16
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, so a manually published version cannot be tied back to a reviewed commit.

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
semgrep semgrep:base64-decode AI (semgrep): Fires in test spec for HMAC verification; legitimate crypto usage, not malicious payload hiding. ai
bogus-package bogus-package AI (bogus-package): Scoped internal package with 503 versions; missing metadata is a stable pattern, not a spam indicator. ai
npm-metadata no-description AI (npm-metadata): Consistent across all versions of this long-lived internal package. ai

Versions (showing 16 of 16)

Version Deps Published
1.72.3 7 / 11
1.72.1 7 / 10
1.72.0 7 / 10
1.71.1 7 / 10
1.71.0 7 / 10
1.70.0 7 / 10
1.69.1 7 / 10
1.69.0 7 / 11
1.68.3 7 / 11
1.68.2 7 / 11
1.68.1 7 / 11
1.68.0 7 / 11
1.67.0 7 / 11
1.66.4 7 / 11
1.66.3 7 / 11
1.66.2 7 / 11

v1.71.1

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.0

1 finding
LOW No provenance attestation provenance

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

v1.69.1

1 finding
LOW No provenance attestation provenance

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

v1.69.0

1 finding
LOW No provenance attestation provenance

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

v1.68.3

1 finding
LOW No provenance attestation provenance

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

v1.68.2

1 finding
LOW No provenance attestation provenance

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

v1.68.1

1 finding
LOW No provenance attestation provenance

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

v1.68.0

1 finding
LOW No provenance attestation provenance

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

v1.67.0

1 finding
LOW No provenance attestation provenance

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

v1.66.4

1 finding
LOW No provenance attestation provenance

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

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