@fleetbase/ember-core No license 21 versions

@fleetbase/ember-core

npm Repository Homepage

21

Versions

—

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

roncodesshivthakker

Keywords

fleetbase-corefleetbase-servicesfleetbaseember-addon

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:ember-concurrency-decorators	AI (phantom-deps): Ember addon convention; config-file references without direct imports are normal for this ecosystem.	ai	2026/05/14
dependencies	unvetted-dep:ember-auto-import	AI (dependencies): Standard Ember addon build tooling; not a runtime risk.	ai	2026/05/11
dependencies	unvetted-dep:ember-cli-htmlbars	AI (dependencies): Standard Ember template compiler; not a runtime risk.	ai	2026/05/11
semgrep	semgrep:dynamic-require	AI (semgrep): Used in has-extension.js to probe for optional packages via try/catch — not a code execution risk.	ai	2026/05/11
phantom-deps	phantom-dep:ember-intl	AI (phantom-deps): Ember addon convention; config-file-only reference is expected for this framework.	ai	2026/05/11
phantom-deps	phantom-dep:@babel/core	AI (phantom-deps): Framework-scoped build tooling; loaded by convention in Ember addons.	ai	2026/05/11
phantom-deps	phantom-dep:ember-loading	AI (phantom-deps): Ember addon config-file reference; standard addon pattern.	ai	2026/05/11
phantom-deps	phantom-dep:ember-wormhole	AI (phantom-deps): Ember addon config-file reference; standard addon pattern.	ai	2026/05/11
phantom-deps	phantom-dep:ember-cli-babel	AI (phantom-deps): Ember build tooling loaded by convention, not direct import.	ai	2026/05/11
phantom-deps	phantom-dep:ember-decorators	AI (phantom-deps): Ember addon convention; config-file-only reference is expected.	ai	2026/05/11
phantom-deps	phantom-dep:ember-auto-import	AI (phantom-deps): Ember build tooling loaded by convention, not direct import.	ai	2026/05/11
phantom-deps	phantom-dep:ember-cli-htmlbars	AI (phantom-deps): Ember build tooling loaded by convention, not direct import.	ai	2026/05/11

Versions (showing 21 of 21)

Version	Deps	Published
0.3.20	18 / 43	2026-06-04
0.3.19	18 / 43	2026-05-11
0.3.18	18 / 43	2026-03-26
0.3.17	18 / 43	2026-03-26
0.3.16	18 / 43	2026-03-26
0.3.15	18 / 43	2026-03-16
0.3.14	18 / 43	2026-03-01
0.3.13	18 / 43	2026-03-01
0.3.12	18 / 43	2026-02-24
0.3.11	18 / 43	2026-02-11
0.3.10	18 / 43	2025-12-29
0.3.9	18 / 43	2025-12-19
0.3.8	18 / 43	2025-12-06
0.3.7	18 / 43	2025-12-05
0.3.6	18 / 43	2025-10-23
0.3.5	18 / 43	2025-10-22
0.3.4	18 / 43	2025-10-20
0.3.3	18 / 43	2025-10-14
0.3.2	18 / 43	2025-05-30
0.3.1	18 / 43	2025-05-23
0.3.0	19 / 43	2025-05-16

v0.3.20

1 finding

LOW No provenance attestation provenance

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

v0.3.19

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.

v0.3.18

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.

v0.3.17

1 finding

LOW No provenance attestation provenance

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

v0.3.16

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.

v0.3.15

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.

v0.3.14

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.

v0.3.13

1 finding

LOW No provenance attestation provenance

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

v0.3.12

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.

v0.3.11

1 finding

LOW No provenance attestation provenance

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

v0.3.10

1 finding

LOW No provenance attestation provenance

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

v0.3.9

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.

v0.3.8

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.

v0.3.7

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.

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.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.

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

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