@sk-web-gui/user-menu
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; missing metadata is a pattern across the @sk-web-gui org, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:@sk-web-gui/logo | AI (phantom-deps): Same-org sibling dep; phantom detection is a heuristic false positive for monorepo packages. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.1.10 | 4 / 1 | |
| 1.1.8 | 4 / 1 | |
| 1.1.7 | 4 / 1 | |
| 1.1.6 | 4 / 1 | |
| 1.1.5 | 4 / 1 | |
| 1.1.4 | 4 / 1 | |
| 1.1.3 | 4 / 1 | |
| 1.1.2 | 4 / 1 | |
| 1.1.1 | 4 / 1 | |
| 1.1.0 | 4 / 1 | |
| 1.0.24 | 4 / 1 | |
| 1.0.23 | 4 / 1 | |
| 1.0.22 | 4 / 1 | |
| 1.0.21 | 4 / 1 | |
| 1.0.20 | 4 / 1 | |
| 1.0.19 | 4 / 1 | |
| 1.0.18 | 4 / 1 | |
| 1.0.17 | 4 / 1 | |
| 1.0.16 | 4 / 1 | |
| 1.0.15 | 4 / 1 | |
| 1.0.14 | 4 / 1 | |
| 1.0.13 | 4 / 1 | |
| 1.0.12 | 4 / 1 |
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
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.
v1.1.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.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
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.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
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.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
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-08-22, 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.0.17
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.0.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 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.
v1.0.15
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-06-13, 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.0.14
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.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.