@awayjs/view
View for AwayJS
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped @awayjs package predates vite; Levenshtein match is coincidental, not a typosquat. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.6.89 | 0 / 12 | |
| 0.6.88 | 0 / 12 | |
| 0.6.87 | 0 / 12 | |
| 0.6.86 | 0 / 12 | |
| 0.6.85 | 0 / 12 | |
| 0.6.84 | 0 / 12 | |
| 0.6.83 | 0 / 12 | |
| 0.6.82 | 0 / 12 | |
| 0.6.81 | 0 / 12 | |
| 0.6.80 | 0 / 12 | |
| 0.6.79 | 0 / 12 | |
| 0.6.78 | 0 / 12 | |
| 0.6.77 | 0 / 12 | |
| 0.6.76 | 0 / 12 | |
| 0.6.75 | 0 / 12 | |
| 0.6.74 | 0 / 12 | |
| 0.6.73 | 0 / 12 | |
| 0.6.72 | 0 / 12 | |
| 0.6.71 | 0 / 12 | |
| 0.6.70 | 0 / 12 | |
| 0.6.69 | 0 / 12 | |
| 0.6.68 | 0 / 12 | |
| 0.6.67 | 0 / 12 | |
| 0.6.66 | 0 / 12 | |
| 0.6.65 | 0 / 12 |
v0.6.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.