@varlock/bumpy
Modern monorepo versioning and changelog tool
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Rapid publish consistent with automated CI/CD pipeline; SLSA attestation confirms legitimate workflow. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from manual (theo) to GitHub Actions CI publishing; backed by SLSA provenance attestation. Expected for this package going forward. | ai | |
| source-diff | obfuscated-file:dist/clack-W95rXis0.mjs | AI (source-diff): Minified bundle output from tsdown build tool; long lines are Unicode lookup tables, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/clack-CehaQZU6.mjs | AI (source-diff): Minified bundle output from tsdown build tool; content is readable Unicode lookup tables, not obfuscated malware. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New dist files are bundled devDependencies (clack, picomatch, semver); expected for a CLI tool. | ai | |
| source-diff | obfuscated-file:dist/clack-C6bVkGxf.mjs | AI (source-diff): Bundled/minified output from tsdown build tool; contains readable third-party library code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/clack-CJT1JFFa.mjs | AI (source-diff): Bundled tsdown output of @clack/prompts; long lines are Unicode lookup tables, not obfuscation. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.13.2 | 0 / 10 | |
| 1.13.1 | 0 / 10 | |
| 1.13.0 | 0 / 10 | |
| 1.12.0 | 0 / 10 | |
| 1.11.0 | 0 / 10 | |
| 1.10.2 | 0 / 10 | |
| 1.10.1 | 0 / 10 | |
| 1.10.0 | 0 / 10 | |
| 1.9.2 | 0 / 10 | |
| 1.9.0 | 0 / 10 | |
| 1.8.1 | 0 / 10 | |
| 1.8.0 | 0 / 10 | |
| 1.7.1 | 0 / 10 | |
| 1.7.0 | 0 / 10 | |
| 1.6.0 | 0 / 10 | |
| 1.5.1 | 0 / 10 | |
| 1.5.0 | 0 / 10 | |
| 1.4.2 | 0 / 10 | |
| 1.4.1 | 0 / 10 | |
| 1.4.0 | 0 / 10 | |
| 1.3.0 | 0 / 10 | |
| 1.2.2 | 0 / 10 | |
| 1.2.1 | 0 / 10 | |
| 1.2.0 | 0 / 10 | |
| 1.1.0 | 0 / 10 | |
| 1.0.0 | 0 / 8 | |
| 0.0.2 | 0 / 8 | |
| 0.0.1 | 0 / 7 |
v1.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.2
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (theo) than the most recent previously approved version (GitHub Actions) on 2026-05-26, but theo 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.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.