@sk-web-gui/core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing metadata fields are expected for internal scoped packages, not spam indicators. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @sk-web-gui design system package; 'core' vs 'cors' is coincidental, not impersonation. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.5.1 | 5 / 4 | |
| 4.5.0 | 5 / 4 | |
| 4.3.2 | 5 / 4 | |
| 4.3.1 | 5 / 4 | |
| 4.3.0 | 5 / 4 | |
| 4.2.0 | 5 / 4 | |
| 4.1.2 | 5 / 4 | |
| 4.1.0 | 5 / 4 | |
| 4.0.0 | 5 / 4 |
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.