ember-file-upload
3
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
jelhanrwwagner90tcemelsumneralonbukaigilest
Keywords
ember-addonfile-upload
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is cosmetic given CI/CD publish with Sigstore. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Legitimate adopted-ember-addons org package with SLSA attestation; dormancy consistent with low-churn addon maintenance. | ai | |
| dependencies | unvetted-dep:ember-auto-import | AI (dependencies): ember-auto-import is a standard Ember ecosystem build tool; stable dependency for this addon. | ai | |
| phantom-deps | phantom-dep:ember-auto-import | AI (phantom-deps): Referenced in config files as expected for an Ember v2 addon; not a real phantom dep. | ai |
v10.1.0
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: GitHub Actions.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.0
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.4.0
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.