@apipass/inputs
This package is a angular component for buttons
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard Angular compiler implicit dep; stable false positive for Angular libraries. | ai | |
| phantom-deps | phantom-dep:jquery | AI (phantom-deps): Referenced in config/build files for ace-builds integration; not a direct import pattern. | ai | |
| phantom-deps | phantom-dep:tinycolor2 | AI (phantom-deps): Used transitively via angular-material-components/color-picker; config-referenced pattern. | ai | |
| phantom-deps | phantom-dep:@ngx-translate/core | AI (phantom-deps): Declared as dep and used in Angular module config; phantom-dep heuristic misfires on Angular DI patterns. | ai | |
| phantom-deps | phantom-dep:@ngx-translate/http-loader | AI (phantom-deps): Same Angular DI/config pattern as @ngx-translate/core; stable false positive. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.0.193 | 17 / 0 | |
| 1.0.192 | 17 / 0 | |
| 1.0.191 | 17 / 0 | |
| 1.0.190 | 17 / 0 | |
| 1.0.189 | 17 / 0 | |
| 1.0.188 | 17 / 0 | |
| 1.0.187 | 17 / 0 | |
| 1.0.186 | 17 / 0 | |
| 1.0.185 | 17 / 0 | |
| 1.0.184 | 17 / 0 | |
| 1.0.183 | 17 / 0 | |
| 1.0.182 | 17 / 0 | |
| 1.0.181 | 17 / 0 | |
| 1.0.180 | 17 / 0 | |
| 1.0.179 | 17 / 0 | |
| 1.0.178 | 17 / 0 | |
| 1.0.177 | 17 / 0 | |
| 1.0.176 | 17 / 0 | |
| 1.0.175 | 17 / 0 | |
| 1.0.174 | 17 / 0 | |
| 1.0.173 | 17 / 0 | |
| 1.0.172 | 17 / 0 | |
| 1.0.171 | 17 / 0 | |
| 1.0.170 | 17 / 0 | |
| 1.0.169 | 17 / 0 | |
| 1.0.167 | 17 / 0 |
v1.0.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.192
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.189
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.188
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.187
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.186
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.185
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.184
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.183
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.182
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.180
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.179
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.178
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.177
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.174
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.173
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.172
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.171
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.170
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.169
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.167
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.