@aurodesignsystem/auro-badge
Auro custom auro-badge 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-badge-D3w9L2WD.js | AI (source-diff): Vite/Rollup minified bundle for a Lit web component; long lines are minified but readable JS, not obfuscation. | ai | |
| phantom-deps | phantom-dep:lit | AI (phantom-deps): lit is a declared runtime dependency and used in the bundled output; phantom-dep fires due to bundling. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 6.2.1 | 1 / 8 | |
| 6.2.0 | 1 / 8 | |
| 6.1.1 | 1 / 8 | |
| 6.1.0 | 1 / 8 | |
| 6.0.0 | 1 / 8 |
v6.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.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.
v6.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.