@botonic/example-flow-builder-typescript
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:he | AI (phantom-deps): Monorepo build dependency; used indirectly via @botonic packages. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Monorepo build dependency; used indirectly via @botonic packages. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Monorepo build dependency; used indirectly via @botonic packages. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): Monorepo build dependency; used indirectly via @botonic packages. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Monorepo build dependency; used indirectly via @botonic packages. | ai | |
| phantom-deps | phantom-dep:react-redux | AI (phantom-deps): Monorepo build dependency; used indirectly via @botonic packages. | ai | |
| phantom-deps | phantom-dep:@reduxjs/toolkit | AI (phantom-deps): Monorepo build dependency; used indirectly via @botonic packages. | ai | |
| phantom-deps | phantom-dep:styled-components | AI (phantom-deps): Monorepo build dependency; used indirectly via @botonic packages. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.49.0 | 16 / 10 | |
| 0.48.0 | 16 / 10 | |
| 0.47.0 | 16 / 10 | |
| 0.46.0 | 16 / 10 | |
| 0.45.0 | 16 / 10 | |
| 0.44.0 | 16 / 10 | |
| 0.43.0 | 16 / 10 | |
| 0.42.0 | 16 / 10 | |
| 0.40.0 | 16 / 10 | |
| 0.39.0 | 16 / 10 | |
| 0.38.0 | 16 / 10 | |
| 0.37.0 | 16 / 10 | |
| 0.36.0 | 12 / 10 | |
| 0.35.0 | 12 / 10 |
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.