← Home

@triptyk/ember-input-validation

npm

This addon will give you an input in TailwindCSS with Ember

14
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

tcdpamaurydremadexdramixdw

Keywords

ember-addon

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Publish hygiene only; no behavioral change, long clean publisher history. ai
phantom-deps phantom-dep:ember-power-select AI (phantom-deps): Config-referenced addon dep, not directly imported; normal for Ember addons. ai
phantom-deps phantom-dep:@eonasdan/tempus-dominus AI (phantom-deps): Config-referenced datepicker dep, not directly imported; normal for Ember addons. ai
phantom-deps phantom-dep:ember-power-select-with-create AI (phantom-deps): Config-referenced addon dep, not directly imported; normal for Ember addons. ai
dependencies unvetted-dep:ember-test-selectors AI (dependencies): ember-test-selectors is a well-known Ember testing utility; stable false positive for this addon. ai
phantom-deps phantom-dep:ember-test-selectors AI (phantom-deps): ember-test-selectors is referenced in config files by convention in Ember addons, not directly imported. ai
phantom-deps phantom-dep:@babel/core AI (phantom-deps): Babel is a build-time tool loaded by convention in Ember addons; not directly imported. ai

Versions (showing 14 of 14)

Version Deps Published
4.0.1 13 / 46
4.0.0 13 / 46
3.0.1 10 / 40
2.0.17 8 / 38
2.0.16 8 / 38
2.0.15 8 / 38
2.0.11 8 / 38
2.0.10 8 / 38
2.0.9 8 / 38
2.0.8 8 / 38
2.0.7 8 / 38
2.0.5 8 / 38
2.0.4 8 / 38
2.0.3 8 / 38

v4.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: remadex → amauryd (on 2026-07-20, known maintainer) provenance

This version was published by a different npm account (amauryd) than the most recent previously approved version (remadex) on 2026-07-20, but amauryd is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.0.17

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: remadex.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.16

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: remadex.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.