@ojiepermana/angular-theme
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:fesm2022/ojiepermana-angular-theme-page-root.mjs | AI (source-diff): Standard Angular fesm2022 bundled/minified output, not real obfuscation. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit Angular/TS runtime dependency. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 22.0.63 | 1 / 0 | |
| 22.0.62 | 1 / 0 | |
| 22.0.61 | 1 / 0 | |
| 22.0.60 | 1 / 0 | |
| 22.0.59 | 1 / 0 | |
| 22.0.58 | 1 / 0 | |
| 22.0.57 | 1 / 0 | |
| 22.0.56 | 1 / 0 | |
| 22.0.54 | 1 / 0 | |
| 22.0.52 | 1 / 0 | |
| 22.0.51 | 1 / 0 | |
| 22.0.49 | 1 / 0 | |
| 22.0.47 | 1 / 0 | |
| 22.0.46 | 1 / 0 | |
| 22.0.45 | 1 / 0 | |
| 22.0.44 | 1 / 0 | |
| 22.0.43 | 1 / 0 | |
| 22.0.41 | 1 / 0 | |
| 22.0.36 | 1 / 0 | |
| 22.0.35 | 1 / 0 | |
| 22.0.34 | 1 / 0 | |
| 22.0.33 | 1 / 0 | |
| 22.0.32 | 1 / 0 | |
| 22.0.29 | 1 / 0 | |
| 22.0.27 | 1 / 0 |
v22.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.61
2 findingsNewly 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.
v22.0.60
2 findingsNewly 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.
v22.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.