← Home

strong-data-uri

npm Repository Homepage

Parser and builder for `data:` URIs

10
Versions
Artistic-2.0
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

0candyamir-61b-admikebajtosdavidcheunghacksparrowjannyhou2016kjdelislekramanqpresleyrfengritchrmgsuperkhauthegmantonyf-ibm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change rmg→bajtos reflects a documented StrongLoop/IBM team transition in 2018; package.json author field explicitly names Miroslav Bajtos (bajtos). Legitimate handoff. ai
maintainer-change maintainer-added AI (maintainer-change): Bulk maintainer additions reflect IBM/StrongLoop org restructuring in 2018, consistent with the package's strongloop GitHub repo and author affiliation. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer removals are part of the same IBM/StrongLoop 2018 team reorganization; no evidence of malicious takeover. ai

Versions (showing 10 of 10)

Version Deps Published
1.0.6 1 / 4
1.0.5 1 / 4
1.0.4 1 / 4
1.0.3 1 / 4
1.0.2 1 / 4
1.0.1 1 / 4
1.0.0 1 / 4
0.2.0 1 / 4
0.1.1 1 / 4
0.1.0 1 / 4

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

2 findings
HIGH Publisher changed: rmg → bajtos (on 2018-02-26) provenance

This version was published by a different npm account than previous versions on 2018-02-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: bajtos → rmg (on 2016-05-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-05-04. This could indicate a legitimate maintainer transition or an account compromise.

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

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