@voiceflow/git-branch-check
Voiceflow branch naming check
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Intentionally minimal internal Voiceflow dev tool; tiny payload and no repo URL are expected for this package. | ai | |
| dependencies | unvetted-dep:current-git-branch | AI (dependencies): current-git-branch is a well-known, stable utility; stable false positive for this dev-tooling package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.6.0 | 1 / 0 | |
| 1.5.0 | 1 / 0 | |
| 1.4.5 | 1 / 0 | |
| 1.4.2 | 1 / 0 | |
| 1.1.3 | 1 / 11 | |
| 1.1.2 | 1 / 11 | |
| 1.1.1 | 1 / 11 | |
| 1.1.0 | 1 / 11 | |
| 1.0.7 | 1 / 11 | |
| 1.0.6 | 1 / 11 | |
| 1.0.5 | 1 / 11 | |
| 1.0.4 | 1 / 11 | |
| 1.0.3 | 1 / 11 | |
| 1.0.2 | 1 / 11 | |
| 1.0.1 | 1 / 11 | |
| 1.0.0 | 1 / 11 |
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (voiceflow-dev) than the most recent previously approved version (tylerhhan) on 2020-04-20, but voiceflow-dev is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (voiceflow-dev) than the most recent previously approved version (tylerhhan) on 2019-11-28, but voiceflow-dev is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tylerhhan) than the most recent previously approved version (voiceflow-dev) on 2019-11-28, but tylerhhan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.