@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 9 of 110)
| Version | Deps | Published |
|---|---|---|
| 0.3.7 | 0 / 1 | |
| 0.3.5 | 0 / 1 | |
| 0.3.4 | 0 / 1 | |
| 0.3.3 | 0 / 1 | |
| 0.3.0 | 0 / 1 | |
| 0.2.8 | 0 / 1 | |
| 0.2.6 | 0 / 1 | |
| 0.2.5 | 0 / 1 | |
| 0.2.4 | 0 / 1 |
v0.3.7
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: ericc59.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
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: ericc59.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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: ericc59.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.