@seniorsistemas/angular-components
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:fesm2022/seniorsistemas-angular-components-spotlight.mjs | AI (source-diff): Standard Angular fesm2022 bundle output; long lines are Angular template compilation artifacts, not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2022/spotlight/lib/spotlight/spotlight-overlay/spotlight-overlay.component.mjs | AI (source-diff): Standard Angular esm2022 compiled component; readable code with JSDoc and normal Angular patterns. | ai | |
| source-diff | obfuscated-file:esm2022/spotlight/lib/spotlight/spotlight-step.directive.mjs | AI (source-diff): Standard Angular directive compiled output; fully readable source. | ai | |
| source-diff | obfuscated-file:esm2022/spotlight/lib/spotlight/spotlight-tour.service.mjs | AI (source-diff): Standard Angular service compiled output; fully readable source. | ai | |
| source-diff | obfuscated-file:esm2022/spotlight/lib/spotlight/spotlight.component.mjs | AI (source-diff): Standard Angular component compiled output; fully readable source. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 19.5.0 | 1 / 0 | |
| 19.4.1 | 1 / 0 | |
| 19.4.0 | 1 / 0 | |
| 19.3.4 | 1 / 0 | |
| 19.3.3 | 1 / 0 | |
| 19.3.2 | 1 / 0 | |
| 19.3.1 | 1 / 0 | |
| 19.3.0 | 1 / 0 | |
| 19.2.0 | 1 / 0 | |
| 19.1.1 | 1 / 0 | |
| 19.1.0 | 1 / 0 | |
| 19.0.9 | 1 / 0 |
v19.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.3.1
6 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.
Newly 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.
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.
v19.3.0
6 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.
Newly 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.
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.
v19.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.