@pylonsync/functions
TypeScript function runtime for pylon — defines server-side queries, mutations, and actions.
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 | rapid-publish | AI (publish-pattern): Package publishes very frequently (289 versions/73 days); expected cadence. | ai | |
| provenance | missing-githead | AI (provenance): Frequent automated releases; benign publish pipeline variance, no malicious payload. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Standard Proxy handler for touch-tracking, not evasion. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): satori/resvg-wasm are well-known OG-image libs matching added SSR image feature. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode of PNG test fixtures in test file. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Test assertion data, not a real network call. | ai | |
| provenance | no-provenance | AI (provenance): Package has no install scripts or obfuscated code; provenance gap alone is not disqualifying for this package. | ai |
Versions (showing 100 of 316)
| Version | Deps | Published |
|---|---|---|
| 0.3.119 | 0 / 1 | |
| 0.3.118 | 0 / 1 | |
| 0.3.116 | 0 / 1 | |
| 0.3.114 | 0 / 1 | |
| 0.3.112 | 0 / 1 | |
| 0.3.110 | 0 / 1 | |
| 0.3.109 | 0 / 1 | |
| 0.3.108 | 0 / 1 | |
| 0.3.107 | 0 / 1 | |
| 0.3.106 | 0 / 1 | |
| 0.3.105 | 0 / 1 | |
| 0.3.104 | 0 / 1 | |
| 0.3.103 | 0 / 1 | |
| 0.3.102 | 0 / 1 | |
| 0.3.101 | 0 / 1 | |
| 0.3.100 | 0 / 1 | |
| 0.3.99 | 0 / 1 | |
| 0.3.98 | 0 / 1 | |
| 0.3.97 | 0 / 1 | |
| 0.3.96 | 0 / 1 | |
| 0.3.95 | 0 / 1 | |
| 0.3.94 | 0 / 1 | |
| 0.3.93 | 0 / 1 | |
| 0.3.92 | 0 / 1 | |
| 0.3.91 | 0 / 1 | |
| 0.3.90 | 0 / 1 | |
| 0.3.89 | 0 / 1 | |
| 0.3.88 | 0 / 1 | |
| 0.3.87 | 0 / 1 | |
| 0.3.86 | 0 / 1 | |
| 0.3.85 | 0 / 1 | |
| 0.3.83 | 0 / 1 | |
| 0.3.79 | 0 / 1 | |
| 0.3.78 | 0 / 1 | |
| 0.3.77 | 0 / 1 | |
| 0.3.76 | 0 / 1 | |
| 0.3.75 | 0 / 1 | |
| 0.3.74 | 0 / 1 | |
| 0.3.73 | 0 / 1 | |
| 0.3.72 | 0 / 1 | |
| 0.3.71 | 0 / 1 | |
| 0.3.70 | 0 / 1 | |
| 0.3.69 | 0 / 1 | |
| 0.3.68 | 0 / 1 | |
| 0.3.67 | 0 / 1 | |
| 0.3.66 | 0 / 1 | |
| 0.3.65 | 0 / 1 | |
| 0.3.64 | 0 / 1 | |
| 0.3.63 | 0 / 1 | |
| 0.3.62 | 0 / 1 | |
| 0.3.61 | 0 / 1 | |
| 0.3.60 | 0 / 1 | |
| 0.3.59 | 0 / 1 | |
| 0.3.58 | 0 / 1 | |
| 0.3.57 | 0 / 1 | |
| 0.3.55 | 0 / 1 | |
| 0.3.54 | 0 / 1 | |
| 0.3.53 | 0 / 1 | |
| 0.3.51 | 0 / 1 | |
| 0.3.50 | 0 / 1 | |
| 0.3.49 | 0 / 1 | |
| 0.3.48 | 0 / 1 | |
| 0.3.47 | 0 / 1 | |
| 0.3.46 | 0 / 1 | |
| 0.3.45 | 0 / 1 | |
| 0.3.44 | 0 / 1 | |
| 0.3.43 | 0 / 1 | |
| 0.3.42 | 0 / 1 | |
| 0.3.41 | 0 / 1 | |
| 0.3.36 | 0 / 1 | |
| 0.3.35 | 0 / 1 | |
| 0.3.34 | 0 / 1 | |
| 0.3.33 | 0 / 1 | |
| 0.3.32 | 0 / 1 | |
| 0.3.31 | 0 / 1 | |
| 0.3.30 | 0 / 1 | |
| 0.3.29 | 0 / 1 | |
| 0.3.28 | 0 / 1 | |
| 0.3.27 | 0 / 1 | |
| 0.3.26 | 0 / 1 | |
| 0.3.25 | 0 / 1 | |
| 0.3.24 | 0 / 1 | |
| 0.3.23 | 0 / 1 | |
| 0.3.22 | 0 / 1 | |
| 0.3.21 | 0 / 1 | |
| 0.3.20 | 0 / 1 | |
| 0.3.19 | 0 / 1 | |
| 0.3.18 | 0 / 1 | |
| 0.3.17 | 0 / 1 | |
| 0.3.16 | 0 / 1 | |
| 0.3.15 | 0 / 1 | |
| 0.3.14 | 0 / 1 | |
| 0.3.13 | 0 / 1 | |
| 0.3.12 | 0 / 1 | |
| 0.3.11 | 0 / 1 | |
| 0.3.10 | 0 / 1 | |
| 0.3.9 | 0 / 1 | |
| 0.3.8 | 0 / 1 | |
| 0.3.7 | 0 / 1 | |
| 0.3.6 | 0 / 1 |
v0.3.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.108
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.