vike-solid
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Manual publish by known co-maintainer, no behavioral change vs prior version. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived low-traffic plugin package; dormancy consistent with maintenance cadence. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established plugin with real functionality; README heuristics are false positive. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.8.3 | 1 / 17 | |
| 0.8.2 | 1 / 17 | |
| 0.8.1 | 1 / 17 | |
| 0.8.0 | 1 / 17 | |
| 0.7.20 | 2 / 16 | |
| 0.7.19 | 2 / 16 | |
| 0.7.18 | 2 / 16 | |
| 0.7.17 | 2 / 16 | |
| 0.7.16 | 2 / 16 | |
| 0.7.15 | 2 / 16 | |
| 0.7.14 | 2 / 16 | |
| 0.7.13 | 2 / 16 | |
| 0.7.12 | 2 / 16 | |
| 0.7.11 | 2 / 16 | |
| 0.7.10 | 2 / 16 | |
| 0.7.9 | 2 / 16 | |
| 0.7.8 | 2 / 16 | |
| 0.7.7 | 2 / 16 | |
| 0.7.6 | 2 / 16 | |
| 0.7.5 | 2 / 17 | |
| 0.7.4 | 1 / 16 | |
| 0.7.3 | 1 / 16 | |
| 0.7.2 | 1 / 16 | |
| 0.7.1 | 1 / 16 | |
| 0.7.0 | 1 / 16 |
v0.7.11
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: brillout.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
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: brillout.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: magne4000.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (magne4000) than the most recent previously approved version (brillout) on 2025-03-10, but magne4000 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.
v0.7.8
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: magne4000.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (magne4000) than the most recent previously approved version (brillout) on 2024-12-19, but magne4000 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.
v0.7.7
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: brillout.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: magne4000.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (magne4000) than the most recent previously approved version (brillout) on 2024-09-29, but magne4000 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.
v0.7.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 (brillout) than the most recent previously approved version (magne4000) on 2024-09-10, but brillout 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.
v0.7.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 (magne4000) than the most recent previously approved version (brillout) on 2024-09-04, but magne4000 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.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.