← Home

@telorun/javascript

npm Repository Homepage

Telo JavaScript module - JavaScript script execution for Telo manifests.

19
Versions
SEE LICENSE IN LICENSE
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

pasi

Keywords

telojavascriptscripting

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:fastify AI (phantom-deps): Config-referenced framework dependency; stable for this package. ai
phantom-deps phantom-dep:@fastify/swagger AI (phantom-deps): Config-referenced plugin; stable for this package. ai
phantom-deps phantom-dep:@sinclair/typebox AI (phantom-deps): Config-referenced schema library; stable for this package. ai
phantom-deps phantom-dep:@scalar/fastify-api-reference AI (phantom-deps): Config-referenced plugin; stable for this package. ai
semgrep semgrep:new-function-constructor AI (semgrep): Core purpose of this package is JS script execution; new Function() is the intentional mechanism for running user scripts. ai

Versions (showing 19 of 19)

Version Deps Published
1.0.0 0 / 2
0.4.0 0 / 2
0.3.0 0 / 2
0.2.2 1 / 2
0.2.1 1 / 2
0.2.0 1 / 2
0.1.13 1 / 2
0.1.12 1 / 2
0.1.11 1 / 2
0.1.10 1 / 2
0.1.9 1 / 2
0.1.8 1 / 2
0.1.7 1 / 2
0.1.6 1 / 2
0.1.5 1 / 2
0.1.4 1 / 2
0.1.3 1 / 2
0.1.2 1 / 2
0.1.0 6 / 2

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.13

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.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.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.1.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.