@sk-web-gui/button
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established org UI library; dormancy followed by maintainer transition is consistent with org handoff, not takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; missing description/repo/keywords is a consistent pattern across the @sk-web-gui namespace, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Same monorepo pattern; stable false positive for this package family. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.1.10 | 4 / 1 | |
| 2.1.9 | 4 / 1 | |
| 2.1.8 | 4 / 1 | |
| 2.1.7 | 4 / 1 | |
| 2.1.6 | 4 / 1 |
v2.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.9
2 findingsThis version was published by a different npm account than previous versions on 2026-02-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.