@sk-web-gui/forms
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/form-control/form-control.js | AI (source-diff): SWC-minified build output, not obfuscation; no malicious behavior. | ai | |
| source-diff | obfuscated-file:dist/esm/form-control/form-control.js | AI (source-diff): SWC-minified build output, not obfuscation; no malicious behavior. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established monorepo component package, missing metadata fields are stylistic not spam. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/modal | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/theme | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/utils | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped UI component package @sk-web-gui/forms; name similarity to cors is coincidental. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/divider | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/popup-menu | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/button | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/icon | AI (dependencies): Same @sk-web-gui monorepo; sibling dep, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/link | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 2.9.3 | 12 / 1 | |
| 2.9.2 | 12 / 1 | |
| 2.9.1 | 12 / 1 | |
| 2.9.0 | 12 / 1 | |
| 2.8.2 | 12 / 1 | |
| 2.8.1 | 12 / 1 | |
| 2.8.0 | 12 / 1 | |
| 2.7.1 | 12 / 1 | |
| 2.7.0 | 12 / 1 | |
| 2.6.1 | 12 / 1 | |
| 2.6.0 | 12 / 1 | |
| 2.5.0 | 12 / 1 | |
| 2.4.5 | 12 / 1 | |
| 2.4.4 | 12 / 1 | |
| 2.4.3 | 12 / 1 | |
| 2.4.2 | 12 / 1 | |
| 2.4.1 | 12 / 1 | |
| 2.4.0 | 12 / 1 | |
| 2.3.0 | 12 / 1 | |
| 2.2.0 | 12 / 1 | |
| 2.1.2 | 6 / 1 | |
| 2.1.1 | 6 / 1 | |
| 2.1.0 | 5 / 1 | |
| 2.0.4 | 5 / 1 | |
| 2.0.3 | 5 / 1 | |
| 2.0.2 | 5 / 1 | |
| 2.0.1 | 5 / 1 | |
| 2.0.0 | 5 / 1 |
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devizetim) than the most recent previously approved version (jerkerosatiesk) on 2025-04-09, but devizetim is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.4.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jerkerosatiesk) than the most recent previously approved version (devizetim) on 2025-03-31, but jerkerosatiesk is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devizetim) than the most recent previously approved version (jerkerosatiesk) on 2025-01-02, but devizetim is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jerkerosatiesk) than the most recent previously approved version (devizetim) on 2024-09-25, but jerkerosatiesk is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devizetim) than the most recent previously approved version (jerkerosatiesk) on 2024-06-18, but devizetim is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jerkerosatiesk) than the most recent previously approved version (devizetim) on 2024-05-27, but jerkerosatiesk is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.