@enablerr-ui/form
enablerr - the Next Enterprise Solution
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped UI component package with 152 versions and 2065-day history; Levenshtein match to 'cors' is coincidental. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 0.2.152 | 0 / 0 | |
| 0.2.151 | 0 / 0 | |
| 0.2.150 | 0 / 0 | |
| 0.2.149 | 0 / 0 | |
| 0.2.148 | 0 / 0 | |
| 0.2.147 | 0 / 0 | |
| 0.2.146 | 0 / 0 | |
| 0.2.145 | 0 / 0 | |
| 0.2.144 | 0 / 0 | |
| 0.2.143 | 0 / 0 | |
| 0.2.142 | 0 / 0 | |
| 0.2.141 | 0 / 0 | |
| 0.2.140 | 0 / 0 | |
| 0.2.139 | 0 / 0 | |
| 0.2.138 | 0 / 0 | |
| 0.2.137 | 0 / 0 | |
| 0.2.136 | 0 / 0 | |
| 0.2.135 | 0 / 0 | |
| 0.2.134 | 0 / 0 | |
| 0.2.133 | 0 / 0 | |
| 0.2.132 | 0 / 0 | |
| 0.2.131 | 0 / 0 | |
| 0.2.130 | 0 / 0 | |
| 0.2.129 | 0 / 0 | |
| 0.2.128 | 0 / 0 | |
| 0.2.127 | 0 / 0 | |
| 0.2.126 | 0 / 0 | |
| 0.2.125 | 0 / 0 | |
| 0.2.124 | 0 / 0 | |
| 0.2.123 | 0 / 0 | |
| 0.2.122 | 0 / 0 | |
| 0.2.121 | 0 / 0 | |
| 0.2.120 | 0 / 0 | |
| 0.2.119 | 0 / 0 | |
| 0.2.118 | 0 / 0 | |
| 0.2.117 | 0 / 0 | |
| 0.2.116 | 0 / 0 | |
| 0.2.115 | 0 / 0 | |
| 0.2.114 | 0 / 0 | |
| 0.2.113 | 0 / 0 | |
| 0.2.112 | 0 / 0 | |
| 0.2.111 | 0 / 0 | |
| 0.2.110 | 0 / 0 | |
| 0.2.109 | 0 / 0 | |
| 0.2.108 | 0 / 0 | |
| 0.2.107 | 0 / 0 | |
| 0.2.106 | 0 / 0 | |
| 0.2.105 | 0 / 0 | |
| 0.2.104 | 0 / 0 |
v0.2.152
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.