← Home

@aurodesignsystem/webcorestylesheets

npm Repository Homepage
10
Versions
—
License
Yes
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

capsule42dale.sandeblackfalconbraven112jordanjones243alaskaairlinesits-admindougalaskarmenner-aa

Keywords

alaska airlinesauro design systemcsssass

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): alaskaairlinesits-admin is an org-level admin account consistent with Alaska Airlines' npm org management pattern. ai
install-scripts install-script:postinstall AI (install-scripts): Postinstall runs a local .mjs script for build/setup; consistent with this Sass UI kit's documented workflow across 60 versions. ai
phantom-deps phantom-dep:@aurodesignsystem/design-tokens AI (phantom-deps): Package is declared as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. ai

Versions (showing 10 of 10)

Version Deps Published
11.1.2 2 / 26
11.0.0 2 / 25
10.1.4 2 / 25
10.1.3 2 / 25
10.1.2 2 / 25
10.1.1 2 / 25
10.0.4 2 / 25
10.0.3 2 / 25
10.0.2 2 / 25
10.0.1 2 / 25

v11.1.2

1 finding
LOW No provenance attestation provenance

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

v11.0.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node packageScripts/postinstall.mjs

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.

v10.1.4

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node packageScripts/postinstall.mjs

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.

v10.1.3

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node packageScripts/postinstall.mjs

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.

v10.1.2

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node packageScripts/postinstall.mjs

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.

v10.1.1

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node packageScripts/postinstall.mjs

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.

v10.0.4

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node packageScripts/postinstall.mjs

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.

v10.0.3

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node packageScripts/postinstall.mjs

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.

v10.0.2

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node packageScripts/postinstall.mjs

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.

v10.0.1

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node packageScripts/postinstall.mjs

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.