@sk-web-gui/popup-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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher jerkerosatiesk has 22 approved packages; consistent with org-internal maintainer transition for @sk-web-gui scope. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established org-scoped component package; missing metadata is a style issue, not a malice indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across this org's packages; not a malice signal. | ai | |
| phantom-deps | phantom-dep:@sk-web-gui/link | AI (phantom-deps): Same-org sibling dep; phantom detection is a heuristic false positive here. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 3.1.10 | 5 / 1 | |
| 3.1.9 | 5 / 1 | |
| 3.1.8 | 5 / 1 | |
| 3.1.7 | 5 / 1 | |
| 3.1.6 | 5 / 1 | |
| 3.1.5 | 5 / 1 | |
| 3.1.4 | 5 / 1 | |
| 3.1.3 | 5 / 1 | |
| 3.1.2 | 5 / 1 | |
| 3.1.1 | 5 / 1 | |
| 3.1.0 | 5 / 1 | |
| 3.0.12 | 5 / 1 | |
| 3.0.11 | 5 / 1 | |
| 3.0.10 | 5 / 1 | |
| 3.0.9 | 5 / 1 | |
| 3.0.8 | 5 / 1 | |
| 3.0.7 | 5 / 1 | |
| 3.0.6 | 5 / 1 | |
| 3.0.5 | 5 / 1 | |
| 3.0.4 | 5 / 1 | |
| 3.0.3 | 5 / 1 | |
| 3.0.2 | 5 / 1 | |
| 3.0.1 | 5 / 1 | |
| 3.0.0 | 5 / 1 |
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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 (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.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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-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.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
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.
v3.0.5
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.
v3.0.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 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.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.