← Home

pinets

npm Repository Homepage
16
Versions
—
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

alaa-eddinesmackey

Keywords

Pine ScriptPinePineScript transpilerPineScript runtimePineScript to JavaScriptPineScript to TypeScriptTradingViewQuantQuantitative FinanceTradingTechnical AnalysisTAIndicatorStrategyBacktestingForecastingMachine LearningData ScienceData AnalysisData VisualizationData Mining

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/pinets.min.browser.es.js AI (source-diff): Minified browser build of a parser/transpiler; large numeric arrays are Unicode tables, not obfuscation. ai
source-diff net-exec-file:dist/pinets.min.browser.es.js AI (source-diff): Browser bundle for a transpiler runtime; network+eval patterns are expected for dynamic script execution in-browser. ai
phantom-deps phantom-dep:acorn AI (phantom-deps): Build-time transpiler dependency; stable pattern for this package. ai
phantom-deps phantom-dep:astring AI (phantom-deps): Build-time code generation dependency; stable pattern for this package. ai
phantom-deps phantom-dep:acorn-walk AI (phantom-deps): Build-time AST traversal dependency; stable pattern for this package. ai

Versions (showing 16 of 16)

Version Deps Published
0.9.19 3 / 21
0.9.18 3 / 21
0.9.17 3 / 21
0.9.16 3 / 21
0.9.15 3 / 21
0.9.14 3 / 21
0.9.13 3 / 21
0.9.12 3 / 21
0.9.11 3 / 21
0.9.10 3 / 21
0.9.9 3 / 21
0.6.1 3 / 13
0.5.0 3 / 13
0.3.0 3 / 13
0.2.1 3 / 12
0.2.0 3 / 12

v0.9.19

1 finding
LOW No provenance attestation provenance

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

v0.9.18

1 finding
LOW No provenance attestation provenance

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

v0.9.17

1 finding
LOW No provenance attestation provenance

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

v0.9.16

1 finding
LOW No provenance attestation provenance

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

v0.9.15

1 finding
LOW No provenance attestation provenance

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

v0.9.14

1 finding
LOW No provenance attestation provenance

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

v0.9.12

3 findings
HIGH New obfuscated file: dist/pinets.min.browser.es.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/pinets.min.browser.es.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.9.11

3 findings
HIGH New obfuscated file: dist/pinets.min.browser.es.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/pinets.min.browser.es.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.9.10

3 findings
HIGH New obfuscated file: dist/pinets.min.browser.es.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/pinets.min.browser.es.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.9.9

3 findings
HIGH New obfuscated file: dist/pinets.min.browser.es.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/pinets.min.browser.es.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.6.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. 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.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.2.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.