@pylonsync/next
Next.js helpers for Pylon — cookie-based auth gate, server-side session helpers, and reusable client hooks.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Scoped package @pylonsync/next is a Next.js helper for Pylon framework; not a typosquat of nuxt. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): 2-edit distance match to jest is coincidental; package is clearly a Next.js/Pylon integration. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): 2-edit distance match to knex is coincidental; package is clearly a Next.js/Pylon integration. | ai |
Versions (showing 51 of 83)
| Version | Deps | Published |
|---|---|---|
| 0.3.85 | 0 / 5 | |
| 0.3.83 | 0 / 5 | |
| 0.3.79 | 0 / 5 | |
| 0.3.78 | 0 / 5 | |
| 0.3.77 | 0 / 5 | |
| 0.3.76 | 0 / 5 | |
| 0.3.75 | 0 / 5 | |
| 0.3.74 | 0 / 5 | |
| 0.3.73 | 0 / 5 | |
| 0.3.72 | 0 / 5 | |
| 0.3.71 | 0 / 5 | |
| 0.3.70 | 0 / 5 | |
| 0.3.69 | 0 / 5 | |
| 0.3.68 | 0 / 5 | |
| 0.3.67 | 0 / 5 | |
| 0.3.66 | 0 / 5 | |
| 0.3.65 | 0 / 5 | |
| 0.3.64 | 0 / 5 | |
| 0.3.63 | 0 / 5 | |
| 0.3.62 | 0 / 5 | |
| 0.3.61 | 0 / 5 | |
| 0.3.60 | 0 / 5 | |
| 0.3.59 | 0 / 5 | |
| 0.3.58 | 0 / 5 | |
| 0.3.57 | 0 / 5 | |
| 0.3.55 | 0 / 5 | |
| 0.3.54 | 0 / 5 | |
| 0.3.53 | 0 / 5 | |
| 0.3.51 | 0 / 5 | |
| 0.3.50 | 0 / 5 | |
| 0.3.49 | 0 / 5 | |
| 0.3.48 | 0 / 5 | |
| 0.3.47 | 0 / 5 | |
| 0.3.46 | 0 / 5 | |
| 0.3.45 | 0 / 5 | |
| 0.3.44 | 0 / 5 | |
| 0.3.43 | 0 / 5 | |
| 0.3.42 | 0 / 5 | |
| 0.3.41 | 0 / 5 | |
| 0.3.36 | 0 / 5 | |
| 0.3.35 | 0 / 5 | |
| 0.3.34 | 0 / 5 | |
| 0.3.33 | 0 / 5 | |
| 0.3.32 | 0 / 5 | |
| 0.3.31 | 0 / 5 | |
| 0.3.30 | 0 / 5 | |
| 0.3.29 | 0 / 5 | |
| 0.3.28 | 0 / 5 | |
| 0.3.27 | 0 / 5 | |
| 0.3.26 | 0 / 5 | |
| 0.3.25 | 0 / 5 |
v0.3.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.