← Home

@ember-data/model

npm Repository Homepage
16
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

ember-data-adminrunspiredrichgthm_krystankatiegengler

Keywords

ember-addon

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation is the expected pattern for this monorepo's automation migration. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects ember-data to warp-drive rebranding; resumed publishing under CI automation with provenance attestation. ai
phantom-deps phantom-dep:@embroider/macros AI (phantom-deps): Build-time macro dependency referenced in config; not directly imported at runtime is expected for ember-addon packages. ai
phantom-deps phantom-dep:@warp-drive/utilities AI (phantom-deps): Sibling monorepo package referenced in config files; phantom-dep false positive for this package structure. ai

Versions (showing 16 of 16)

Version Deps Published
5.8.2 8 / 8
5.8.1 8 / 8
5.7.0 8 / 8
5.6.0 8 / 8
5.5.0 6 / 19
5.4.1 6 / 20
5.3.13 6 / 20
5.3.12 6 / 20
5.3.11 6 / 21
5.3.10 6 / 21
5.3.9 6 / 21
5.3.8 6 / 21
5.3.7 6 / 21
5.3.6 6 / 21
5.3.5 6 / 21
5.3.4 6 / 21

v5.5.0

1 finding
LOW No provenance attestation provenance

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

v5.4.1

1 finding
LOW No provenance attestation provenance

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

v5.3.13

1 finding
LOW No provenance attestation provenance

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

v5.3.12

1 finding
LOW No provenance attestation provenance

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

v5.3.11

1 finding
LOW No provenance attestation provenance

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

v5.3.10

1 finding
LOW No provenance attestation provenance

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

v5.3.9

1 finding
LOW No provenance attestation provenance

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

v5.3.8

1 finding
LOW No provenance attestation provenance

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

v5.3.7

1 finding
LOW No provenance attestation provenance

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

v5.3.6

1 finding
LOW No provenance attestation provenance

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

v5.3.5

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.

v5.3.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.