@flows/js
Flows JS SDK - Build native product growth experiences, your way
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is confirmed legitimate by SLSA provenance attestation on this and likely future versions. | ai | |
| dependencies | unvetted-dep:@lit-labs/preact-signals | AI (dependencies): @lit-labs/preact-signals is a legitimate Google/Lit Labs package; stable dependency for this SDK. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @flows/js is not a typosquat of pg; false positive for this SDK. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Scoped package @flows/js is not a typosquat of rxjs; false positive for this SDK. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @flows/js is not a typosquat of qs; name reflects the flows SDK identity. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @flows/js is not a typosquat of ajv; false positive for this SDK. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @flows/js is not a typosquat of joi; false positive for this SDK. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped package @flows/js is not a typosquat of jest; false positive for this SDK. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.22.0 | 5 / 8 | |
| 1.21.2 | 5 / 8 | |
| 1.21.1 | 5 / 8 | |
| 1.21.0 | 5 / 8 | |
| 1.20.0 | 5 / 9 | |
| 1.19.4 | 5 / 9 | |
| 1.19.3 | 5 / 9 | |
| 1.19.2 | 5 / 9 | |
| 1.19.1 | 5 / 9 | |
| 1.19.0 | 5 / 9 | |
| 1.18.2 | 5 / 9 | |
| 1.18.1 | 5 / 9 | |
| 1.18.0 | 5 / 9 | |
| 1.17.1 | 5 / 9 | |
| 1.17.0 | 5 / 9 | |
| 1.16.1 | 5 / 9 | |
| 1.16.0 | 5 / 9 | |
| 1.15.1 | 5 / 9 | |
| 1.15.0 | 5 / 9 | |
| 1.14.1 | 2 / 7 | |
| 1.14.0 | 2 / 7 | |
| 1.13.1 | 1 / 7 | |
| 1.13.0 | 1 / 7 | |
| 1.12.0 | 1 / 7 | |
| 1.11.0 | 1 / 7 | |
| 1.10.3 | 1 / 7 | |
| 1.10.2 | 1 / 7 | |
| 1.10.1 | 1 / 7 | |
| 1.10.0 | 1 / 7 | |
| 1.9.2 | 1 / 7 | |
| 1.9.1 | 1 / 7 |
v1.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.0
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.20.0
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.3
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
2 findingsPackage name '@flows/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.