inline-source-map MIT 19 versions

inline-source-map

npm Repository Homepage

Adds source mappings and base64 encodes them, so they can be inlined in your generated file.

19

Versions

MIT

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

zertoshthlorenz

Keywords

sourcemapinlinebase64bundlegeneratetranspile

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): thlorenz is the original author of this package (repo URL, author field, and homepage all reference thlorenz). The publisher change from zertosh to thlorenz represents the original author reclaiming the package, not a hostile takeover.	ai	2026/04/23
publish-pattern	dormant-publish	AI (publish-pattern): Package is a mature 13-year-old utility. Dormancy is consistent with stability, not takeover. The original author (thlorenz) published with only minor test script cleanup.	ai	2026/04/23

Versions (showing 19 of 19)

Version	Deps	Published
0.6.3	1 / 2	2024-02-24
0.6.2	1 / 2	2016-04-13
0.6.1	1 / 2	2015-10-04
0.6.0	1 / 2	2015-07-17
0.5.0	1 / 2	2015-02-27
0.4.1	1 / 2	2015-02-19
0.4.0	1 / 2	2015-02-19
0.3.1	1 / 2	2015-02-19
0.3.0	1 / 2	2013-11-05
0.2.5	1 / 2	2013-07-06
0.2.4	1 / 1	2013-07-06
0.2.3	1 / 1	2013-03-27
0.2.2	1 / 1	2013-03-17
0.2.1	1 / 1	2013-03-11
0.2.0	1 / 1	2013-03-11
0.1.3	1 / 1	2013-03-10
0.1.2	1 / 1	2013-03-09
0.1.1	1 / 1	2013-03-07
0.1.0	1 / 1	2013-03-07

v0.6.3

2 findings

HIGH Publisher changed: zertosh → thlorenz (on 2024-02-24) provenance

This version was published by a different npm account than previous versions on 2024-02-24. 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.

v0.6.2

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: thlorenz → zertosh (on 2016-04-13) provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

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

1 finding

LOW No provenance attestation provenance

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

v0.1.2

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. Consider requesting the maintainer enable provenance via CI/CD.

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.