← Home

@squiz/component-logger-lib

npm
5
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
publish-pattern dormant-publish AI (publish-pattern): Long-lived internal package with sparse release cadence, no behavioral signal. ai
maintainer-change maintainer-added AI (maintainer-change): Org-managed publisher rotation, not indicative of takeover. ai
bogus-package bogus-package AI (bogus-package): Internal scoped lib lacking metadata polish, not spam. ai

Versions (showing 5 of 5)

Version Deps Published
1.71.4 3 / 4
1.71.3 3 / 4
1.71.2 3 / 4
1.71.1 2 / 6
1.71.0 2 / 6

v1.71.3

1 finding
LOW No provenance attestation provenance

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

v1.71.2

1 finding
LOW No provenance attestation provenance

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

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