@aurodesignsystem/wc-generator
Boilerplate generator for Auro Web Components
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): WC generator CLI legitimately uses child_process to scaffold and run commands; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@aurodesignsystem/auro-library | AI (phantom-deps): Declared in template package.json scaffold output, not a direct import; stable false positive for this generator package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.7.1 | 6 / 9 | |
| 4.7.0 | 6 / 9 | |
| 4.6.2 | 6 / 9 | |
| 4.6.1 | 6 / 9 | |
| 4.6.0 | 5 / 10 | |
| 4.5.9 | 5 / 10 | |
| 4.5.8 | 5 / 10 |
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.