← Home

@lindorm/pylon

npm Repository Homepage

HTTP and WebSocket application framework for Node.js, built on Koa and Socket.IO and wired into the Lindorm ecosystem.

10
Versions
AGPL-3.0-or-later
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

princejonn

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@lindorm/aes AI (phantom-deps): Re-exported by @lindorm/aegis; stable pattern for this monorepo. ai
phantom-deps phantom-dep:@lindorm/okp AI (phantom-deps): Re-exported by @lindorm/aegis; stable pattern for this monorepo. ai
phantom-deps phantom-dep:@lindorm/rsa AI (phantom-deps): Re-exported by @lindorm/aegis; stable pattern for this monorepo. ai
phantom-deps phantom-dep:@lindorm/ec AI (phantom-deps): Re-exported by @lindorm/aegis; stable pattern for this monorepo. ai
phantom-deps phantom-dep:@lindorm/oct AI (phantom-deps): Re-exported by @lindorm/aegis; stable pattern for this monorepo. ai
phantom-deps phantom-dep:@lindorm/enums AI (phantom-deps): Same-org sibling dep; likely re-exported via types rather than direct import. Stable false positive. ai
phantom-deps phantom-dep:busboy AI (phantom-deps): busboy is a declared runtime dep used for multipart parsing; phantom-dep heuristic false positive. ai

Versions (showing 10 of 10)

Version Deps Published
0.12.0 27 / 16
0.11.3 27 / 16
0.6.0 23 / 22
0.5.1 23 / 22
0.5.0 23 / 22
0.4.4 29 / 11
0.4.3 29 / 11
0.4.2 29 / 11
0.4.1 29 / 11
0.4.0 28 / 11

v0.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.3

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.4

1 finding
LOW No provenance attestation provenance

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

v0.4.3

1 finding
LOW No provenance attestation provenance

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

v0.4.2

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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