@rango-dev/provider-solflare MIT 18 versions

@rango-dev/provider-solflare

npm

Solflare integration for hub. [Homepage](https://solflare.com/) | [Docs](https://docs.solflare.com/)

18

Versions

MIT

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

yeager-eren

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/mod.js	AI (source-diff): dist/mod.js is a standard minified ESM bundle with readable logic; not obfuscated malware.	ai	2026/05/02
publish-pattern	dormant-publish	AI (publish-pattern): Large established monorepo with 138 versions; dormancy likely reflects release cadence, not takeover.	ai	2026/04/30
bogus-package	bogus-package	AI (bogus-package): Rango-dev workspace packages consistently lack repo/homepage metadata; not indicative of spam.	ai	2026/04/28
phantom-deps	phantom-dep:@solana/web3.js	AI (phantom-deps): @solana/web3.js is declared as a dependency in package.json; phantom-dep is a false positive here.	ai	2026/04/28

Versions (showing 18 of 18)

Version	Deps	Published
0.27.0	6 / 0	2026-05-31
0.26.1	6 / 0	2026-05-02
0.26.0	6 / 0	2026-04-29
0.25.0	6 / 0	2025-12-30
0.24.0	6 / 0	2025-12-15
0.23.0	6 / 0	2025-12-09
0.22.0	6 / 0	2025-12-02
0.21.1	6 / 0	2025-11-22
0.19.0	6 / 0	2025-10-29
0.18.0	6 / 0	2025-09-29
0.17.0	6 / 0	2025-09-06
0.16.0	6 / 0	2025-08-19
0.15.0	6 / 0	2025-08-05
0.14.0	6 / 0	2025-07-22
0.13.0	6 / 0	2025-07-09
0.12.0	6 / 0	2025-06-09
0.11.1	6 / 0	2025-05-04
0.11.0	6 / 0	2025-04-30

v0.27.0

1 finding

LOW No provenance attestation provenance

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

v0.26.1

1 finding

LOW No provenance attestation provenance

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

v0.25.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.24.0

2 findings

HIGH New obfuscated file: dist/mod.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.

LOW No provenance attestation provenance

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

v0.23.0

2 findings

HIGH New obfuscated file: dist/mod.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.

LOW No provenance attestation provenance

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

v0.22.0

1 finding

LOW No provenance attestation provenance

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

v0.21.1

1 finding

LOW No provenance attestation provenance

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

v0.19.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.18.0

1 finding

LOW No provenance attestation provenance

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

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

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