vue-class-component
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/vue-class-component.esm-browser.prod.js | AI (source-diff): Minified rollup build output, not obfuscation; recurring in every prod dist file. | ai | |
| source-diff | obfuscated-file:dist/vue-class-component.global.prod.js | AI (source-diff): Minified rollup build output, not obfuscation; recurring in every prod dist file. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 7.2.6 | 0 / 33 | |
| 7.2.5 | 0 / 33 | |
| 7.2.4 | 0 / 33 | |
| 7.2.3 | 0 / 33 | |
| 7.2.2 | 0 / 32 | |
| 7.2.1 | 0 / 32 | |
| 7.2.0 | 0 / 30 | |
| 7.1.0 | 0 / 30 | |
| 7.0.2 | 0 / 30 | |
| 7.0.1 | 0 / 30 | |
| 7.0.0 | 0 / 30 |
v7.2.5
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.
v7.2.4
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.
v7.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.