@rip-lang/server
Bun-native content server: static sites, apps, HTTP proxy, and TCP/TLS passthrough
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party same-org packages, not unrelated third-party libs. | ai | |
| dependencies | unvetted-dep:@rip-lang/api | AI (dependencies): Same-org workspace dependency within the rip-lang monorepo; expected. | ai | |
| phantom-deps | phantom-dep:@rip-lang/api | AI (phantom-deps): Same-scope workspace dep referenced indirectly; stable FP. | ai | |
| phantom-deps | phantom-dep:@rip-lang/validate | AI (phantom-deps): Package uses .rip files; JS import analysis cannot detect usage in non-JS source files. Same org scope confirms intentional dep. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped @rip-lang package; name reflects its purpose (server), not an attempt to impersonate semver. | ai | |
| phantom-deps | phantom-dep:rip-lang | AI (phantom-deps): rip-lang is the runtime for .rip files; referenced in config/build scripts rather than JS imports — stable false positive for this package. | ai |
Versions (showing 65 of 65)
| Version | Deps | Published |
|---|---|---|
| 1.4.28 | 1 / 0 | |
| 1.4.27 | 1 / 0 | |
| 1.4.26 | 1 / 0 | |
| 1.4.25 | 1 / 0 | |
| 1.4.24 | 1 / 0 | |
| 1.4.23 | 1 / 0 | |
| 1.4.22 | 1 / 0 | |
| 1.4.21 | 1 / 0 | |
| 1.4.20 | 1 / 0 | |
| 1.4.18 | 1 / 0 | |
| 1.4.17 | 1 / 0 | |
| 1.4.16 | 1 / 0 | |
| 1.4.15 | 1 / 0 | |
| 1.4.14 | 1 / 0 | |
| 1.4.13 | 1 / 0 | |
| 1.4.12 | 1 / 0 | |
| 1.4.11 | 1 / 0 | |
| 1.4.10 | 1 / 0 | |
| 1.4.9 | 1 / 0 | |
| 1.4.8 | 1 / 0 | |
| 1.4.7 | 1 / 0 | |
| 1.4.6 | 1 / 0 | |
| 1.4.5 | 1 / 0 | |
| 1.4.4 | 1 / 0 | |
| 1.4.3 | 1 / 0 | |
| 1.4.2 | 1 / 0 | |
| 1.4.1 | 1 / 0 | |
| 1.3.126 | 1 / 0 | |
| 1.3.125 | 1 / 0 | |
| 1.3.4 | 1 / 0 | |
| 1.2.5 | 2 / 0 | |
| 1.2.2 | 2 / 0 | |
| 1.2.0 | 2 / 0 | |
| 1.1.18 | 2 / 0 | |
| 1.1.15 | 2 / 0 | |
| 1.1.3 | 2 / 0 | |
| 1.1.0 | 2 / 0 | |
| 1.0.1 | 2 / 0 | |
| 1.0.0 | 2 / 0 | |
| 0.8.3 | 0 / 0 | |
| 0.8.2 | 0 / 0 | |
| 0.8.1 | 0 / 0 | |
| 0.8.0 | 0 / 0 | |
| 0.7.11 | 0 / 0 | |
| 0.7.10 | 0 / 0 | |
| 0.7.9 | 0 / 0 | |
| 0.7.8 | 0 / 0 | |
| 0.7.7 | 0 / 0 | |
| 0.7.6 | 0 / 0 | |
| 0.7.5 | 0 / 0 | |
| 0.7.4 | 0 / 0 | |
| 0.7.3 | 0 / 0 | |
| 0.7.2 | 0 / 0 | |
| 0.7.1 | 0 / 0 | |
| 0.7.0 | 0 / 0 | |
| 0.6.1 | 0 / 0 | |
| 0.6.0 | 0 / 0 | |
| 0.5.7 | 0 / 0 | |
| 0.5.6 | 0 / 0 | |
| 0.5.5 | 0 / 0 | |
| 0.5.4 | 0 / 0 | |
| 0.5.3 | 0 / 0 | |
| 0.5.2 | 0 / 0 | |
| 0.5.1 | 0 / 0 | |
| 0.5.0 | 0 / 0 |
v1.4.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
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: shreeve.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
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: shreeve.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
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: shreeve.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
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: shreeve.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
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: shreeve.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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: shreeve.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.