flow-parser
JavaScript parser written in OCaml. Produces ESTree AST
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): marcoww has been the publisher for 411 approved versions over 133 days; legitimate maintainer transition for facebook/flow. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): marcoww is the established publisher for flow-parser; maintainer addition is a legitimate team transition. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): flow-parser uses 0.0.0 as a documented stub/placeholder version. Package is 11 years old with 6M weekly downloads — not a throwaway. | ai | |
| bogus-package | bogus-package | AI (bogus-package): flow-parser is a legitimate high-traffic package (6M downloads/week). Its minimal metadata and tiny payload reflect its role as a compiled OCaml wrapper stub, not spam. | ai |
Versions (showing 100 of 417)
| Version | Deps | Published |
|---|---|---|
| 0.316.0 | 0 / 4 | |
| 0.315.0 | 0 / 4 | |
| 0.314.0 | 0 / 4 | |
| 0.313.0 | 0 / 4 | |
| 0.312.1 | 0 / 4 | |
| 0.312.0 | 0 / 4 | |
| 0.311.0 | 0 / 4 | |
| 0.310.0 | 0 / 4 | |
| 0.309.0 | 0 / 4 | |
| 0.308.0 | 0 / 4 | |
| 0.307.1 | 0 / 4 | |
| 0.307.0 | 0 / 4 | |
| 0.306.1 | 0 / 4 | |
| 0.306.0 | 0 / 4 | |
| 0.305.1 | 0 / 4 | |
| 0.305.0 | 0 / 4 | |
| 0.304.0 | 0 / 4 | |
| 0.303.0 | 0 / 4 | |
| 0.302.0 | 0 / 4 | |
| 0.301.0 | 0 / 4 | |
| 0.300.0 | 0 / 4 | |
| 0.299.0 | 0 / 4 | |
| 0.298.0 | 0 / 4 | |
| 0.297.0 | 0 / 4 | |
| 0.296.1 | 0 / 4 | |
| 0.296.0 | 0 / 4 | |
| 0.295.0 | 0 / 4 | |
| 0.294.0 | 0 / 4 | |
| 0.293.0 | 0 / 4 | |
| 0.292.0 | 0 / 4 | |
| 0.291.0 | 0 / 4 | |
| 0.290.0 | 0 / 4 | |
| 0.289.0 | 0 / 4 | |
| 0.288.0 | 0 / 4 | |
| 0.287.0 | 0 / 4 | |
| 0.286.0 | 0 / 4 | |
| 0.285.0 | 0 / 4 | |
| 0.284.0 | 0 / 4 | |
| 0.283.0 | 0 / 4 | |
| 0.282.0 | 0 / 4 | |
| 0.281.0 | 0 / 4 | |
| 0.280.0 | 0 / 4 | |
| 0.279.0 | 0 / 4 | |
| 0.278.0 | 0 / 4 | |
| 0.277.1 | 0 / 4 | |
| 0.277.0 | 0 / 4 | |
| 0.276.0 | 0 / 4 | |
| 0.275.0 | 0 / 4 | |
| 0.274.2 | 0 / 4 | |
| 0.274.1 | 0 / 4 | |
| 0.274.0 | 0 / 4 | |
| 0.273.1 | 0 / 4 | |
| 0.273.0 | 0 / 4 | |
| 0.272.2 | 0 / 4 | |
| 0.272.1 | 0 / 4 | |
| 0.272.0 | 0 / 4 | |
| 0.271.0 | 0 / 4 | |
| 0.270.0 | 0 / 4 | |
| 0.269.1 | 0 / 4 | |
| 0.268.0 | 0 / 4 | |
| 0.267.0 | 0 / 4 | |
| 0.266.1 | 0 / 4 | |
| 0.266.0 | 0 / 4 | |
| 0.265.3 | 0 / 4 | |
| 0.265.2 | 0 / 4 | |
| 0.265.0 | 0 / 4 | |
| 0.264.0 | 0 / 4 | |
| 0.263.0 | 0 / 4 | |
| 0.262.0 | 0 / 4 | |
| 0.261.2 | 0 / 4 | |
| 0.261.1 | 0 / 4 | |
| 0.261.0 | 0 / 4 | |
| 0.260.0 | 0 / 4 | |
| 0.259.1 | 0 / 4 | |
| 0.259.0 | 0 / 4 | |
| 0.258.1 | 0 / 4 | |
| 0.258.0 | 0 / 4 | |
| 0.257.1 | 0 / 4 | |
| 0.257.0 | 0 / 4 | |
| 0.256.0 | 0 / 4 | |
| 0.255.0 | 0 / 4 | |
| 0.254.2 | 0 / 4 | |
| 0.254.1 | 0 / 4 | |
| 0.254.0 | 0 / 4 | |
| 0.253.0 | 0 / 4 | |
| 0.252.0 | 0 / 4 | |
| 0.251.1 | 0 / 4 | |
| 0.251.0 | 0 / 4 | |
| 0.250.0 | 0 / 4 | |
| 0.249.0 | 0 / 4 | |
| 0.248.1 | 0 / 4 | |
| 0.248.0 | 0 / 4 | |
| 0.247.1 | 0 / 4 | |
| 0.247.0 | 0 / 4 | |
| 0.246.0 | 0 / 4 | |
| 0.245.2 | 0 / 4 | |
| 0.245.1 | 0 / 4 | |
| 0.245.0 | 0 / 4 | |
| 0.244.0 | 0 / 4 | |
| 0.243.0 | 0 / 4 |
v0.316.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.315.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.314.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.313.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.312.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.312.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.311.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.310.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.309.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.308.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.307.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.307.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.306.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.306.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.305.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.305.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.304.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.303.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.302.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.301.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.300.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.299.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.298.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.297.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.296.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.296.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.295.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.294.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.293.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.292.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.291.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.290.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.289.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.288.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.287.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.286.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.285.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.284.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.283.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.282.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.281.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.280.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.279.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.278.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.277.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.277.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.276.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.275.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.273.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.273.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.272.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.272.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.272.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.271.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.270.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.269.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.268.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.267.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.266.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.266.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.265.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.265.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.265.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.264.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.263.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.262.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.261.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.261.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.261.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.260.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.259.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.259.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.258.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.258.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.257.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.257.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.256.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.255.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.254.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.254.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.254.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.253.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.252.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.251.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.251.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.250.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.249.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.248.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.248.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.247.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.247.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.246.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.245.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.245.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.245.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.244.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.243.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.