@brillout/vite-plugin-server-entry
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Long-established package with no description; stable false positive for this package. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.7.19 | 2 / 6 | |
| 0.7.18 | 2 / 6 | |
| 0.7.17 | 2 / 6 | |
| 0.7.16 | 2 / 6 | |
| 0.7.15 | 2 / 6 | |
| 0.7.14 | 2 / 6 | |
| 0.7.13 | 2 / 6 | |
| 0.7.12 | 2 / 6 | |
| 0.7.11 | 2 / 6 | |
| 0.7.10 | 2 / 6 | |
| 0.7.9 | 2 / 6 | |
| 0.7.8 | 2 / 6 | |
| 0.7.7 | 2 / 6 | |
| 0.7.6 | 2 / 6 | |
| 0.7.5 | 2 / 6 | |
| 0.7.4 | 2 / 6 | |
| 0.7.3 | 2 / 6 | |
| 0.7.2 | 2 / 6 | |
| 0.7.1 | 2 / 6 | |
| 0.7.0 | 2 / 6 | |
| 0.6.3 | 2 / 6 | |
| 0.6.2 | 2 / 6 | |
| 0.6.1 | 2 / 6 | |
| 0.6.0 | 2 / 6 | |
| 0.5.8 | 2 / 6 | |
| 0.5.7 | 2 / 6 | |
| 0.5.6 | 2 / 6 | |
| 0.5.5 | 2 / 6 | |
| 0.5.4 | 1 / 6 | |
| 0.5.3 | 1 / 6 | |
| 0.5.2 | 1 / 6 | |
| 0.5.1 | 1 / 6 | |
| 0.5.0 | 1 / 6 | |
| 0.4.13 | 1 / 6 | |
| 0.4.12 | 1 / 6 | |
| 0.4.11 | 1 / 6 | |
| 0.4.10 | 1 / 6 | |
| 0.4.9 | 1 / 6 | |
| 0.4.8 | 1 / 4 | |
| 0.4.7 | 1 / 4 |
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.