@velajs/vela
NestJS-compatible framework for edge runtimes, powered by Hono
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@velajs/errors | AI (dependencies): First-party @velajs sibling package, same org/monorepo as vela. | ai | |
| provenance | missing-githead | AI (provenance): Benign publish-env variance for an actively-developed framework with clean history. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Growth matches new feature modules (exports list expanded), not injected code. | ai | |
| dependencies | unvetted-dep:@velajs/live-protocol | AI (dependencies): First-party sibling package under same @velajs org, not third-party risk. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party monorepo sibling, low risk. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Publisher has strong track record; rapid publish consistent with CI automation, not malicious pattern. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 1.19.0 | 3 / 12 | |
| 1.18.0 | 2 / 12 | |
| 1.17.1 | 2 / 12 | |
| 1.17.0 | 2 / 12 | |
| 1.16.0 | 1 / 12 | |
| 1.15.0 | 1 / 11 | |
| 1.14.0 | 1 / 11 | |
| 1.13.0 | 1 / 11 | |
| 1.12.0 | 1 / 11 | |
| 1.10.0 | 1 / 11 | |
| 1.9.0 | 1 / 10 | |
| 1.8.8 | 1 / 10 | |
| 1.8.7 | 1 / 10 | |
| 1.8.5 | 1 / 10 | |
| 1.8.4 | 1 / 10 | |
| 1.8.3 | 1 / 10 | |
| 1.8.2 | 1 / 10 | |
| 1.8.1 | 1 / 10 | |
| 1.8.0 | 1 / 10 | |
| 1.6.0 | 1 / 10 | |
| 1.5.1 | 1 / 10 | |
| 1.5.0 | 1 / 10 | |
| 1.4.1 | 1 / 10 | |
| 1.4.0 | 1 / 10 | |
| 1.3.0 | 1 / 10 | |
| 1.2.0 | 1 / 7 | |
| 1.1.0 | 1 / 7 | |
| 1.0.0 | 1 / 7 | |
| 0.10.0 | 1 / 7 | |
| 0.9.0 | 1 / 7 | |
| 0.8.0 | 1 / 7 | |
| 0.7.0 | 1 / 7 | |
| 0.6.1 | 1 / 7 | |
| 0.6.0 | 1 / 7 | |
| 0.5.2 | 1 / 7 | |
| 0.5.1 | 1 / 7 | |
| 0.5.0 | 1 / 7 | |
| 0.4.3 | 1 / 7 | |
| 0.4.2 | 1 / 7 | |
| 0.4.1 | 1 / 6 | |
| 0.4.0 | 1 / 6 | |
| 0.3.0 | 1 / 6 | |
| 0.2.1 | 1 / 6 | |
| 0.2.0 | 1 / 6 | |
| 0.1.0 | 1 / 6 |
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.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: kauandotnet.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.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: kauandotnet.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.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: kauandotnet.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.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: kauandotnet.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.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: kauandotnet.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.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: kauandotnet.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.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: kauandotnet.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.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: kauandotnet.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
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: kauandotnet.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.