← Home

@freik/seqnum

npm Repository Homepage

A simple Sequence Number generator

23
Versions
Unlicense
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

freik

Keywords

js-utils

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Likely a toolchain change (bun-based build); package is a trivial utility with no malicious indicators. ai

Versions (showing 23 of 23)

Version Deps Published
1.3.10 0 / 9
1.3.9 0 / 9
1.3.7 0 / 9
1.3.6 0 / 9
1.3.5 0 / 9
1.3.4 0 / 9
1.3.3 0 / 9
1.3.2 0 / 9
1.3.1 0 / 9
1.2.1 0 / 9
1.2.0 0 / 9
1.1.24 0 / 9
1.1.23 0 / 9
1.1.21 0 / 9
1.1.20 0 / 9
1.1.19 0 / 9
1.1.18 0 / 9
1.1.17 0 / 9
1.1.16 0 / 9
1.1.15 0 / 9
1.1.14 0 / 9
1.1.12 0 / 9
1.1.11 0 / 15

v1.1.17

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: freik.

v1.1.16

1 finding
LOW No provenance attestation provenance

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

v1.1.15

1 finding
LOW No provenance attestation provenance

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

v1.1.14

1 finding
LOW No provenance attestation provenance

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

v1.1.12

1 finding
LOW No provenance attestation provenance

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

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