@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 16 of 316)
| Version | Deps | Published |
|---|---|---|
| 0.3.5 | 0 / 1 | |
| 0.3.4 | 0 / 1 | |
| 0.3.3 | 0 / 1 | |
| 0.3.2 | 0 / 1 | |
| 0.3.1 | 0 / 1 | |
| 0.3.0 | 0 / 1 | |
| 0.2.16 | 0 / 1 | |
| 0.2.15 | 0 / 1 | |
| 0.2.12 | 0 / 1 | |
| 0.2.11 | 0 / 1 | |
| 0.2.10 | 0 / 1 | |
| 0.2.9 | 0 / 1 | |
| 0.2.8 | 0 / 1 | |
| 0.2.6 | 0 / 1 | |
| 0.2.5 | 0 / 1 | |
| 0.2.4 | 0 / 1 |
v0.3.2
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.1
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.2.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.2.15
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.2.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.2.11
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.2.10
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.2.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.