@flipt-io/flipt-client-js
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/browser/index.cjs | AI (source-diff): Base64-encoded WASM binary inlined by @rollup/plugin-wasm; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/node/index.cjs | AI (source-diff): Base64-encoded WASM binary inlined by @rollup/plugin-wasm; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/browser/index.mjs | AI (source-diff): Base64-encoded WASM binary inlined by @rollup/plugin-wasm; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/node/index.mjs | AI (source-diff): Base64-encoded WASM binary inlined by @rollup/plugin-wasm; stable pattern for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 1 / 20 | |
| 0.4.1 | 1 / 20 | |
| 0.4.0 | 1 / 20 | |
| 0.3.0 | 1 / 20 | |
| 0.2.0 | 1 / 20 | |
| 0.1.0 | 1 / 20 | |
| 0.0.6 | 1 / 17 | |
| 0.0.5 | 1 / 17 |
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
5 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.