@abhinav2203/codeflow-core
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tree-sitter-c | AI (phantom-deps): Indirect dependency used via web-tree-sitter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tree-sitter-go | AI (phantom-deps): Indirect dependency used via web-tree-sitter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tree-sitter-cpp | AI (phantom-deps): Indirect dependency used via web-tree-sitter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tree-sitter-rust | AI (phantom-deps): Indirect dependency used via web-tree-sitter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tree-sitter-python | AI (phantom-deps): Indirect dependency used via web-tree-sitter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tree-sitter-javascript | AI (phantom-deps): Indirect dependency used via web-tree-sitter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tree-sitter-typescript | AI (phantom-deps): Indirect dependency used via web-tree-sitter; stable pattern for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.1.6 | 10 / 3 | |
| 1.1.5 | 10 / 3 | |
| 1.1.4 | 10 / 3 | |
| 1.1.2 | 10 / 3 | |
| 1.1.1 | 10 / 3 | |
| 1.0.2 | 10 / 3 | |
| 1.0.1 | 10 / 3 | |
| 1.0.0 | 10 / 3 | |
| 0.1.1 | 2 / 2 | |
| 0.1.0 | 2 / 2 |
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.