@aurodesignsystem/auro-nav
auro-nav HTML custom element
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/auro-nav-BkZmGtok.js | AI (source-diff): Standard Vite/Rollup minified bundle of Lit web components; not obfuscated, stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:lit | AI (phantom-deps): lit is a runtime dependency used in the bundled dist output; phantom-dep heuristic false positive for bundled packages. | ai | |
| source-diff | obfuscated-file:dist/auro-nav-DjBuYPdo.js | AI (source-diff): Standard Vite/Rollup minified bundle for a Lit web component; content-hashed filename is normal build output for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.1.1 | 1 / 9 | |
| 4.1.0 | 1 / 9 | |
| 4.0.2 | 1 / 9 | |
| 4.0.1 | 1 / 9 | |
| 4.0.0 | 1 / 9 |
v4.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.