@sk-web-gui/list
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @sk-web-gui package; 2-edit distance to 'jest' is coincidental, not a typosquat attempt. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.2.9 | 2 / 1 | |
| 1.2.8 | 2 / 1 | |
| 1.2.7 | 2 / 1 | |
| 1.2.6 | 2 / 1 | |
| 1.2.5 | 2 / 1 | |
| 1.2.4 | 2 / 1 | |
| 1.2.3 | 2 / 1 | |
| 1.2.2 | 2 / 1 | |
| 1.2.1 | 2 / 1 | |
| 1.2.0 | 2 / 1 | |
| 1.1.16 | 2 / 1 | |
| 1.1.15 | 2 / 1 | |
| 1.1.14 | 2 / 1 | |
| 1.1.13 | 2 / 1 | |
| 1.1.12 | 2 / 1 | |
| 1.1.11 | 2 / 1 | |
| 1.1.10 | 2 / 1 | |
| 1.1.9 | 2 / 1 | |
| 1.1.8 | 2 / 1 | |
| 1.1.7 | 2 / 1 | |
| 1.1.6 | 2 / 1 |
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.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 (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.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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-30, 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.
v1.1.16
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.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
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.
v1.1.12
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-05, 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.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
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-08-06, 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.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
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.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.