@fleetbase/fleetops-data
Fleetbase Fleet-Ops based models, serializers, transforms, adapters and GeoJson utility functions.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:ember-cli-htmlbars | AI (dependencies): ember-cli-htmlbars is a standard Ember CLI build tool; its use here is expected for an Ember addon. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has prior approvals; no material changes from last version; consistent with irregular release cadence for this org's addon. | ai | |
| provenance | no-provenance | AI (provenance): Established Fleetbase org package; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Standard Ember addon convention; @babel/core is framework-scoped and not directly imported. | ai | |
| phantom-deps | phantom-dep:ember-cli-babel | AI (phantom-deps): Referenced in Ember config files by convention; not a real phantom dep for Ember addons. | ai | |
| phantom-deps | phantom-dep:ember-cli-htmlbars | AI (phantom-deps): Referenced in Ember config files by convention; standard Ember addon pattern. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.1.36 | 5 / 39 | |
| 0.1.35 | 5 / 39 | |
| 0.1.34 | 5 / 39 | |
| 0.1.33 | 5 / 39 | |
| 0.1.32 | 5 / 39 | |
| 0.1.31 | 5 / 39 | |
| 0.1.30 | 5 / 39 | |
| 0.1.29 | 5 / 39 | |
| 0.1.28 | 5 / 39 | |
| 0.1.27 | 5 / 39 | |
| 0.1.26 | 5 / 39 | |
| 0.1.25 | 5 / 39 | |
| 0.1.24 | 5 / 39 | |
| 0.1.23 | 5 / 39 | |
| 0.1.22 | 5 / 39 | |
| 0.1.21 | 5 / 39 | |
| 0.1.20 | 5 / 39 |
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.