← Home

@aurodesignsystem/auro-icon

5
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

capsule42dale.sandeblackfalconbraven112jordanjones243alaskaairlinesits-admindougalaskarmenner-aa

Keywords

alaska airlinesaurodesign systemweb components

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/auro-icon-Q-6YPBJ5.js AI (source-diff): Minified LitElement bundle with inline SVG icon data; expected build output for this design-system component package. ai
source-diff obfuscated-file:dist/auro-icon-C0vUd7Ip.js AI (source-diff): Standard Vite/Rollup minified bundle with LitElement and inline SVG; not obfuscated malware. ai
phantom-deps phantom-dep:lit AI (phantom-deps): lit is a declared runtime dependency and is bundled into the dist output; phantom-dep is a false positive here. ai

Versions (showing 5 of 5)

Version Deps Published
9.2.0 1 / 8
9.1.2 1 / 8
9.1.1 1 / 8
9.1.0 1 / 8
9.0.0 1 / 8

v9.2.0

2 findings
HIGH New obfuscated file: dist/auro-icon-C0vUd7Ip.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v9.1.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v9.1.1

2 findings
HIGH New obfuscated file: dist/auro-icon-Q-6YPBJ5.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v9.1.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.

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