flowgen
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): Publisher change from joarwilk to orta is a documented legitimate maintainer transition. Orta is a highly reputable npm publisher with 1470 approved packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): orta is a well-known, trusted npm publisher. This addition reflects a legitimate maintainer transition, not a compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): shelljs and prettier are well-established, widely-used packages with no malicious history. Their addition is consistent with flowgen's code generation purpose. | ai | |
| dependencies | unvetted-dep:paralleljs | AI (dependencies): paralleljs is a legitimate parallel computing library with no malicious indicators; unvetted status is a registry gap, not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:babel-preset-stage-2 | AI (phantom-deps): babel-preset-stage-2 is a well-known Babel preset; phantom-dep finding reflects packaging hygiene, not a security issue. | ai | |
| phantom-deps | phantom-dep:jest | AI (phantom-deps): jest is a dev tool incorrectly listed as a runtime dep; it's a well-known test framework with no security risk. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:babel-cli | AI (phantom-deps): babel-cli is a build tool incorrectly listed as a runtime dep; well-known package with no security risk. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:paralleljs | AI (phantom-deps): paralleljs is a legitimate parallel processing library; phantom-dep finding reflects packaging hygiene, not a security issue. | ai | |
| phantom-deps | phantom-dep:esformatter | AI (phantom-deps): esformatter is a well-known JS formatter; phantom-dep finding reflects packaging hygiene, not a security issue. | ai | |
| phantom-deps | phantom-dep:babel-preset-react | AI (phantom-deps): babel-preset-react is a well-known Babel preset; phantom-dep finding reflects packaging hygiene, not a security issue. | ai | |
| phantom-deps | phantom-dep:babel-preset-es2015 | AI (phantom-deps): babel-preset-es2015 is a well-known Babel preset; phantom-dep finding reflects packaging hygiene, not a security issue. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process import is in lib/test-matchers.js, a test helper used to invoke the flowgen CLI during testing. This is expected behavior for a CLI tool's test suite. | ai | |
| dependencies | unvetted-dep:typescript-compiler | AI (dependencies): typescript-compiler is a thin CLI wrapper for TypeScript, consistent with flowgen's purpose of parsing TypeScript definitions. No meaningful risk. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 1.21.0 | 8 / 26 | |
| 1.20.1 | 8 / 26 | |
| 1.20.0 | 8 / 26 | |
| 1.19.0 | 8 / 26 | |
| 1.18.0 | 8 / 26 | |
| 1.17.0 | 8 / 26 | |
| 1.16.2 | 8 / 26 | |
| 1.16.1 | 8 / 26 | |
| 1.16.0 | 8 / 26 | |
| 1.15.0 | 8 / 25 | |
| 1.14.1 | 8 / 25 | |
| 1.14.0 | 8 / 25 | |
| 1.13.0 | 8 / 25 | |
| 1.12.1 | 8 / 23 | |
| 1.12.0 | 8 / 23 | |
| 1.11.0 | 8 / 17 | |
| 1.10.0 | 9 / 30 | |
| 1.9.2 | 9 / 29 | |
| 1.9.1 | 9 / 29 | |
| 1.9.0 | 9 / 29 | |
| 1.8.4 | 7 / 28 | |
| 1.8.3 | 7 / 28 | |
| 1.8.2 | 7 / 28 | |
| 1.8.1 | 7 / 28 | |
| 1.8.0 | 7 / 28 | |
| 1.7.0 | 7 / 28 | |
| 1.6.0 | 7 / 28 | |
| 1.5.8 | 7 / 25 | |
| 1.5.7 | 7 / 25 | |
| 1.5.6 | 7 / 25 | |
| 1.5.5 | 7 / 25 | |
| 1.5.4 | 7 / 25 | |
| 1.5.3 | 7 / 25 | |
| 1.5.2 | 7 / 25 | |
| 1.5.1 | 7 / 25 | |
| 1.5.0 | 7 / 25 | |
| 1.4.1 | 7 / 18 | |
| 1.4.0 | 7 / 18 | |
| 1.3.0 | 7 / 6 | |
| 1.2.3 | 7 / 6 | |
| 1.2.2 | 6 / 6 | |
| 1.2.1 | 6 / 6 | |
| 1.2.0 | 12 / 0 | |
| 1.1.0 | 12 / 0 | |
| 1.0.1 | 12 / 0 | |
| 1.0.0 | 12 / 0 |
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
2 findingsThis version was published by a different npm account than previous versions on 2019-02-06. 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.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: orta.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
2 findingsThis version was published by a different npm account than previous versions on 2019-02-06. 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.
v1.5.3
2 findingsThis version was published by a different npm account than previous versions on 2019-02-04. 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.
v1.5.2
2 findingsThis version was published by a different npm account than previous versions on 2019-02-04. 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.
v1.5.1
2 findingsThis version was published by a different npm account than previous versions on 2019-02-04. 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.
v1.5.0
2 findingsThis version was published by a different npm account than previous versions on 2019-02-04. 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.
v1.4.1
2 findingsThis version was published by a different npm account than previous versions on 2019-02-03. 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.
v1.4.0
2 findingsThis version was published by a different npm account than previous versions on 2019-01-31. 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.
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2018-10-15. 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.
v1.2.3
2 findingsThis version was published by a different npm account than previous versions on 2018-09-10. 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.
v1.2.2
2 findingsThis version was published by a different npm account than previous versions on 2018-05-07. 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.
v1.2.1
2 findingsThis version was published by a different npm account than previous versions on 2018-03-12. 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.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.