← Home

@pylonsync/functions

TypeScript function runtime for pylon — defines server-side queries, mutations, and actions.

100
Versions
MIT OR Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

ericc59

Keywords

pylontypescriptfunctionsdatabase

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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.243 0 / 1
0.3.242 0 / 1
0.3.241 0 / 1
0.3.240 0 / 1
0.3.239 0 / 1
0.3.238 0 / 1
0.3.237 0 / 1
0.3.236 0 / 1
0.3.235 0 / 1
0.3.234 0 / 1
0.3.233 0 / 1
0.3.232 0 / 1
0.3.231 0 / 1
0.3.230 0 / 1
0.3.229 0 / 1
0.3.228 0 / 1
0.3.227 0 / 1
0.3.226 0 / 1
0.3.225 0 / 1
0.3.224 0 / 1
0.3.223 0 / 1
0.3.222 0 / 1
0.3.220 0 / 1
0.3.218 0 / 1
0.3.216 0 / 1
0.3.215 0 / 1
0.3.213 0 / 1
0.3.212 0 / 1
0.3.211 0 / 1
0.3.210 0 / 1
0.3.209 0 / 1
0.3.208 0 / 1
0.3.207 0 / 1
0.3.206 0 / 1
0.3.205 0 / 1
0.3.203 0 / 1
0.3.202 0 / 1
0.3.201 0 / 1
0.3.200 0 / 1
0.3.198 0 / 1
0.3.197 0 / 1
0.3.196 0 / 1
0.3.195 0 / 1
0.3.193 0 / 1
0.3.192 0 / 1
0.3.189 0 / 1
0.3.188 0 / 1
0.3.187 0 / 1
0.3.186 0 / 1
0.3.185 0 / 1
0.3.184 0 / 1
0.3.183 0 / 1
0.3.182 0 / 1
0.3.181 0 / 1
0.3.180 0 / 1
0.3.179 0 / 1
0.3.178 0 / 1
0.3.177 0 / 1
0.3.176 0 / 1
0.3.174 0 / 1
0.3.173 0 / 1
0.3.172 0 / 1
0.3.171 0 / 1
0.3.170 0 / 1
0.3.169 0 / 1
0.3.168 0 / 1
0.3.167 0 / 1
0.3.166 0 / 1
0.3.165 0 / 1
0.3.163 0 / 1
0.3.162 0 / 1
0.3.161 0 / 1
0.3.158 0 / 1
0.3.157 0 / 1
0.3.155 0 / 1
0.3.154 0 / 1
0.3.153 0 / 1
0.3.152 0 / 1
0.3.151 0 / 1
0.3.149 0 / 1
0.3.147 0 / 1
0.3.146 0 / 1
0.3.144 0 / 1
0.3.142 0 / 1
0.3.140 0 / 1
0.3.139 0 / 1
0.3.138 0 / 1
0.3.137 0 / 1
0.3.136 0 / 1
0.3.135 0 / 1
0.3.134 0 / 1
0.3.133 0 / 1
0.3.131 0 / 1
0.3.130 0 / 1
0.3.129 0 / 1
0.3.127 0 / 1
0.3.126 0 / 1
0.3.124 0 / 1
0.3.123 0 / 1
0.3.121 0 / 1
Showing 100 of 316 Next page →

v0.3.158

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.157

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.155

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.154

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.153

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.152

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.151

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.147

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.139

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.135

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.134

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.133

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.131

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.130

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.129

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.124

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.123

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.121

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.