← Home

@izara_project/izara-shared-search-and-sort

npm Repository Homepage

Shared Libraries frontend/backend for Search and Sort stack

11
Versions
AGPL-3.0-or-later
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

sventhebarbarian

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Internal org library; sparse README and no keywords are expected for private/scoped packages, not spam indicators. ai
phantom-deps phantom-dep:@izara_project/izara-shared AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for transitive/re-exported org packages. ai
phantom-deps phantom-dep:@izara_project/izara-core-library-external-request AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for transitive/re-exported org packages. ai
phantom-deps phantom-dep:object-hash AI (phantom-deps): Config-referenced utility; stable pattern for this package. ai
phantom-deps phantom-dep:@izara_project/izara-core-library-core AI (phantom-deps): Same-org internal dependency; expected for shared library. ai
phantom-deps phantom-dep:@izara_project/izara-shared-service-schemas AI (phantom-deps): Same-org internal dependency; expected for shared library. ai

Versions (showing 11 of 11)

Version Deps Published
1.0.16 3 / 1
1.0.15 3 / 1
1.0.14 3 / 1
1.0.13 3 / 1
1.0.12 3 / 1
1.0.11 3 / 1
1.0.10 3 / 1
1.0.9 3 / 1
1.0.8 3 / 1
1.0.3 6 / 1
1.0.2 6 / 1

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

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

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

v1.0.13

1 finding
LOW No provenance attestation provenance

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

v1.0.12

1 finding
LOW No provenance attestation provenance

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

v1.0.11

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.

v1.0.10

1 finding
LOW No provenance attestation provenance

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

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

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

v1.0.3

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.

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