← Home

@nectary/labs

Welcome to Nectary Labs! This is the experimental playground for new components, patterns, and features that are being evaluated for inclusion in the main Nectary design system.

32
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

pbricoutdeepsweetolivercarlssonwhncararo_sinchminademian

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Org-scoped package with no provenance; consistent across all 146 versions, not a risk indicator here. ai

Versions (showing 32 of 132)

Version Deps Published
2.5.16 1 / 5
2.5.15 1 / 5
2.5.14 1 / 5
2.5.13 1 / 5
2.5.12 1 / 5
2.5.11 1 / 5
2.5.10 1 / 5
2.5.9 1 / 5
2.5.8 1 / 5
2.5.7 1 / 5
2.5.6 1 / 5
2.5.5 1 / 5
2.5.4 1 / 5
2.5.3 1 / 5
2.5.2 1 / 5
2.5.1 1 / 5
2.5.0 1 / 5
2.4.5 1 / 5
2.4.4 1 / 5
2.4.3 1 / 5
2.4.2 1 / 5
2.4.1 1 / 5
2.4.0 1 / 5
2.0.9 1 / 6
2.0.8 1 / 6
2.0.7 1 / 6
2.0.6 1 / 6
2.0.5 1 / 6
2.0.3 1 / 6
2.0.2 1 / 6
2.0.1 1 / 6
2.0.0 1 / 6

v2.0.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.