@getpaseo/server
Paseo backend server
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@getpaseo/client | AI (phantom-deps): Same-org package; phantom-dep heuristic unreliable for monorepo siblings. | ai | |
| phantom-deps | phantom-dep:fast-uri | AI (phantom-deps): fast-uri is a transitive/config dep; phantom-dep false positive stable for this package. | ai | |
| phantom-deps | phantom-dep:@deepgram/sdk | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lezer/common | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tiny-invariant | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:express-basic-auth | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:strip-ansi | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@mariozechner/pi-agent-core | AI (phantom-deps): Conditionally loaded agent core dependency; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@mariozechner/pi-ai | AI (phantom-deps): Conditionally loaded AI provider dependency; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:sherpa-onnx-node | AI (phantom-deps): sherpa-onnx-node is a speech/ASR native module used conditionally; phantom-dep heuristic fires on optional/config-driven imports. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): @getpaseo/server is a scoped backend package for the Paseo product; 'server' vs 'semver' is a coincidental Levenshtein match, not impersonation. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 0.1.90 | 34 / 11 | |
| 0.1.89 | 34 / 11 | |
| 0.1.88 | 34 / 11 | |
| 0.1.87 | 34 / 11 | |
| 0.1.86 | 34 / 11 | |
| 0.1.85 | 34 / 11 | |
| 0.1.84 | 34 / 11 | |
| 0.1.83 | 34 / 11 | |
| 0.1.82 | 34 / 11 | |
| 0.1.81 | 34 / 11 | |
| 0.1.80 | 34 / 11 | |
| 0.1.79 | 34 / 11 | |
| 0.1.78 | 37 / 11 | |
| 0.1.77 | 37 / 11 | |
| 0.1.76 | 37 / 11 | |
| 0.1.75 | 37 / 11 | |
| 0.1.74 | 37 / 11 | |
| 0.1.73 | 37 / 11 | |
| 0.1.72 | 37 / 11 | |
| 0.1.71 | 37 / 11 | |
| 0.1.70 | 37 / 11 | |
| 0.1.69 | 36 / 11 | |
| 0.1.68 | 36 / 11 | |
| 0.1.67 | 36 / 11 | |
| 0.1.66 | 35 / 11 | |
| 0.1.65 | 35 / 11 | |
| 0.1.63 | 34 / 11 | |
| 0.1.62 | 38 / 12 | |
| 0.1.61 | 38 / 12 | |
| 0.1.60 | 38 / 12 | |
| 0.1.59 | 37 / 12 | |
| 0.1.58 | 37 / 12 | |
| 0.1.57 | 37 / 12 | |
| 0.1.56 | 36 / 12 | |
| 0.1.55 | 36 / 12 | |
| 0.1.54 | 35 / 12 | |
| 0.1.53 | 35 / 12 | |
| 0.1.52 | 34 / 12 | |
| 0.1.51 | 34 / 12 | |
| 0.1.50 | 34 / 12 | |
| 0.1.49 | 34 / 12 | |
| 0.1.48 | 34 / 12 | |
| 0.1.47 | 35 / 12 | |
| 0.1.46 | 35 / 12 | |
| 0.1.45 | 35 / 12 | |
| 0.1.44 | 34 / 12 | |
| 0.1.43 | 34 / 11 | |
| 0.1.42 | 33 / 11 | |
| 0.1.41 | 33 / 11 | |
| 0.1.40 | 33 / 11 | |
| 0.1.39 | 33 / 11 |
v0.1.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.63
2 findingsPackage name '@getpaseo/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
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: boudra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
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: boudra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.