backport Apache-2.0 5 versions

backport

npm Repository Homepage

A CLI tool that automates the process of backporting commits

5

Versions

Apache-2.0

License

Yes

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

sqren

Keywords

backportbackportingversioningcherry-pickgitgit-cherry-pickcliautomationproductivitybranchesbranching

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:dedent	AI (phantom-deps): dedent is a declared runtime dep used via config/codegen tooling; stable false positive.	ai	2026/05/12
phantom-deps	phantom-dep:graphql-tag	AI (phantom-deps): graphql-tag declared as runtime dep, used via codegen config; stable false positive.	ai	2026/05/12
phantom-deps	phantom-dep:safe-json-stringify	AI (phantom-deps): safe-json-stringify declared as runtime dep; stable false positive.	ai	2026/05/12
install-scripts	install-script:postinstall	AI (install-scripts): Guarded postinstall only runs a local dist script if present; benign pattern stable across versions.	ai	2026/05/12
phantom-deps	phantom-dep:dotenv	AI (phantom-deps): dotenv is a declared runtime dependency used via config files; phantom-dep heuristic is a false positive here.	ai	2026/05/12

Versions (showing 5 of 5)

Version	Deps	Published
12.0.0	18 / 27	2026-05-03
11.0.2	18 / 27	2026-04-08
11.0.1	18 / 27	2026-03-18
11.0.0	18 / 27	2026-03-16
10.4.0	22 / 34	2026-02-25

v12.0.0

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: test -f ./dist/src/scripts/run-postinstall.js && node ./dist/src/scripts/run-postinstall.js || echo 'Dist folder missing'

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.

v11.0.2

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: test -f ./dist/src/scripts/run-postinstall.js && node ./dist/src/scripts/run-postinstall.js || echo 'Dist folder missing'

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.

v11.0.1

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: test -f ./dist/src/scripts/run-postinstall.js && node ./dist/src/scripts/run-postinstall.js || echo 'Dist folder missing'

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.

v11.0.0

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: test -f ./dist/src/scripts/run-postinstall.js && node ./dist/src/scripts/run-postinstall.js || echo 'Dist folder missing'

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.

v10.4.0

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: test -f ./dist/src/scripts/run-postinstall.js && node ./dist/src/scripts/run-postinstall.js || echo 'Dist folder missing'

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.