@web-atoms/data-styles
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Build script loads files by constructed path; stable build-tool pattern for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 0 / 1 | |
| 1.1.2 | 0 / 1 | |
| 1.0.132 | 0 / 1 | |
| 1.0.129 | 0 / 1 | |
| 1.0.125 | 0 / 1 | |
| 1.0.124 | 0 / 1 | |
| 1.0.123 | 0 / 1 | |
| 1.0.122 | 0 / 1 | |
| 1.0.121 | 0 / 1 | |
| 1.0.120 | 0 / 1 | |
| 1.0.119 | 0 / 1 | |
| 1.0.118 | 0 / 1 |
v1.0.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.