@hyperdrive.bot/bmad-workflow MIT 19 versions

@hyperdrive.bot/bmad-workflow

npm Repository Homepage

AI-driven development workflow orchestration CLI for BMAD projects

19

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

marcelodevsquad

Keywords

cliworkfloworchestrationaibmadoclif

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:uuid	AI (phantom-deps): uuid is legitimately declared and used by this CLI; phantom-dep rule is a false positive for oclif-based packages.	ai	2026/04/27
phantom-deps	phantom-dep:bcrypt	AI (phantom-deps): bcrypt is legitimately declared and used by this CLI; phantom-dep rule is a false positive for oclif-based packages.	ai	2026/04/27
phantom-deps	phantom-dep:nodemailer	AI (phantom-deps): nodemailer is legitimately declared and used by this CLI; phantom-dep rule is a false positive for oclif-based packages.	ai	2026/04/27
phantom-deps	phantom-dep:jsonwebtoken	AI (phantom-deps): jsonwebtoken is legitimately declared and used by this CLI; phantom-dep rule is a false positive for oclif-based packages.	ai	2026/04/27
phantom-deps	phantom-dep:@oclif/plugin-help	AI (phantom-deps): Explicitly declared in oclif.plugins configuration; phantom-dep rule is a false positive for oclif framework packages.	ai	2026/04/27

Versions (showing 19 of 19)

Version	Deps	Published
1.0.40	20 / 29	2026-05-11
1.0.39	20 / 29	2026-05-10
1.0.38	20 / 29	2026-05-09
1.0.18	16 / 29	2026-02-15
1.0.17	15 / 29	2026-02-11
1.0.16	15 / 29	2026-02-11
1.0.15	15 / 29	2026-02-11
1.0.14	15 / 29	2026-02-11
1.0.13	15 / 29	2026-02-06
1.0.12	15 / 29	2026-02-06
1.0.11	15 / 29	2026-02-05
1.0.10	15 / 29	2026-02-05
1.0.9	15 / 29	2026-02-05
1.0.8	15 / 29	2026-02-05
1.0.7	15 / 29	2026-02-05
1.0.6	15 / 28	2026-02-05
1.0.4	15 / 28	2026-01-20
1.0.3	15 / 28	2026-01-20
1.0.2	15 / 29	2026-01-19

v1.0.40

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.39

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.38

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.