← Home

@deijose/nix-ionic

npm Repository Homepage

Ionic lifecycle & router bridge for Nix.js

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

Maintainers

deijose

Keywords

ionicnix-jsbridgeroutingnavigationlifecyclecapacitormobilenativeiosandroidweb-componentsreactivesignalstypescriptmicro-frameworkuifrontendtree-shakingmodular

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/lib/tabs-Dqk41O69.cjs AI (source-diff): Minified by terser as documented in build:lib script; content is benign Ionic lifecycle/router code. ai
source-diff obfuscated-file:dist/lib/components.cjs AI (source-diff): Minified by terser per documented build script; content is Ionic component re-exports, no malicious patterns. ai
source-diff obfuscated-file:dist/lib/tabs-D6BxA_bp.cjs AI (source-diff): Minified by terser per documented build script; content is routing/lifecycle bridge logic, no malicious patterns. ai

Versions (showing 33 of 33)

Version Deps Published
1.4.6 2 / 6
1.4.5 2 / 6
1.4.4 2 / 6
1.4.3 2 / 6
1.4.2 2 / 6
1.4.1 2 / 6
1.4.0 2 / 6
1.3.3 2 / 6
1.3.2 2 / 6
1.3.1 2 / 6
1.3.0 2 / 6
1.2.1 2 / 6
1.2.0 3 / 5
1.0.1 3 / 5
1.0.0 3 / 5
0.5.2 3 / 5
0.5.1 3 / 5
0.5.0 3 / 5
0.4.1 3 / 5
0.4.0 3 / 5
0.3.3 3 / 5
0.3.2 3 / 5
0.3.0 3 / 5
0.2.0 3 / 5
0.1.8 2 / 5
0.1.7 2 / 5
0.1.6 2 / 5
0.1.5 2 / 5
0.1.4 0 / 6
0.1.3 0 / 6
0.1.2 0 / 6
0.1.1 0 / 6
0.1.0 0 / 6

v1.4.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.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

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

1 finding
LOW No provenance attestation provenance

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

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