launch-editor-middleware
express middleware for launching editor
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Metadata gap only, no behavioral change; stable trusted package. | ai | |
| provenance | publisher-changed | AI (provenance): Package migrated to GitHub Actions CI publishing with SLSA attestation; consistent with vitejs org practices. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sapphi-red is a known Vite core contributor; legitimate maintainer addition for vitejs org package. | ai | |
| dependencies | unvetted-dep:launch-editor | AI (dependencies): launch-editor is a sibling package in the same monorepo by the same author; dependency is expected and stable. | ai | |
| provenance | no-provenance | AI (provenance): Mature, well-known package; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2.14.1 | 1 / 0 | |
| 2.14.0 | 1 / 0 | |
| 2.13.2 | 1 / 0 | |
| 2.13.1 | 1 / 0 | |
| 2.13.0 | 1 / 0 | |
| 2.12.0 | 1 / 0 | |
| 2.11.1 | 1 / 0 | |
| 2.11.0 | 1 / 0 | |
| 2.10.0 | 1 / 0 | |
| 2.9.1 | 1 / 0 | |
| 2.9.0 | 1 / 0 | |
| 2.8.1 | 1 / 0 | |
| 2.8.0 | 1 / 0 | |
| 2.7.0 | 1 / 0 | |
| 2.6.1 | 1 / 0 | |
| 2.6.0 | 1 / 0 | |
| 2.5.0 | 1 / 0 | |
| 2.4.0 | 1 / 0 | |
| 2.3.0 | 1 / 0 | |
| 2.2.1 | 1 / 0 | |
| 2.2.0 | 1 / 0 | |
| 2.1.0 | 1 / 0 | |
| 2.0.0 | 1 / 0 |
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: soda.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: soda.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: soda.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
2 findingsThis version was published by a different npm account (soda) than the most recent previously approved version (yyx990803) on 2021-12-21. It has since remained available on npm for 1679 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.