@conterra/vuln-scan
con terra vulnerability scan process
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/add-project-to-vex.js | AI (source-diff): esbuild-minified CLI bundle; code content is legitimate vuln-scan tooling, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/jira-reporter.js | AI (source-diff): esbuild-minified CLI bundle; code content is legitimate Jira issue-creation logic. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop reflects switch to dist-only esbuild output; expected for this build pattern. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.10 | 1 / 17 | |
| 1.0.9 | 1 / 17 | |
| 1.0.8 | 1 / 17 | |
| 0.0.34 | 1 / 16 | |
| 0.0.33 | 1 / 16 | |
| 0.0.32 | 1 / 16 | |
| 0.0.31 | 1 / 16 | |
| 0.0.30 | 1 / 16 |
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.