← Home

@endo/base64

npm Repository Homepage
15
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

kriskowalmichaelfigerightswarnermhofmanboneskullnaugturturadgakriscendobot

Keywords

base64endoses

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): boneskull is a well-established npm publisher (105 approved packages) taking over from kriskowal within the same endojs/endo monorepo org. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects the monorepo's release cadence, not account takeover; publisher identity and repo URL are consistent. ai

Versions (showing 15 of 15)

Version Deps Published
1.1.1 0 / 0
1.1.0 0 / 0
1.0.12 0 / 10
1.0.11 0 / 10
1.0.10 0 / 10
1.0.9 0 / 10
1.0.8 0 / 10
1.0.7 0 / 10
1.0.6 0 / 10
1.0.5 0 / 10
1.0.4 0 / 10
1.0.3 0 / 10
1.0.2 0 / 10
1.0.1 0 / 10
1.0.0 0 / 10

v1.0.9

1 finding
LOW No provenance attestation provenance

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

v1.0.8

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

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

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

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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