rollup-plugin-typescript MIT 20 versions

rollup-plugin-typescript

npm Repository Homepage

Seamless integration between Rollup and TypeScript.

20

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

paulbgdrich_harristrysoundvictorystick

Keywords

rollup-plugintypescriptes2015

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from trysound to lukastaegert is a documented legitimate transfer to the Rollup core maintainer; package lives under the official rollup GitHub org.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): paulbgd and rich_harris are known Rollup ecosystem contributors; addition reflects legitimate team expansion under the rollup GitHub org.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): resolve is a widely-trusted, well-established npm package; its addition is consistent with the plugin's module resolution functionality.	ai	2026/04/24

Versions (showing 20 of 20)

Version	Deps	Published
1.0.1	2 / 9	2019-03-24
1.0.0	2 / 9	2018-09-16
0.8.1	5 / 6	2016-08-17
0.8.0	5 / 4	2016-08-17
0.7.7	5 / 3	2016-07-18
0.7.6	5 / 3	2016-06-19
0.7.5	5 / 3	2016-04-25
0.7.3	5 / 3	2016-04-19
0.7.2	5 / 3	2016-04-19
0.7.1	5 / 3	2016-04-19
0.7.0	5 / 3	2016-04-14
0.6.1	5 / 3	2016-04-01
0.6.0	5 / 3	2016-03-07
0.5.0	4 / 3	2016-01-23
0.4.1	4 / 3	2016-01-22
0.4.0	4 / 3	2016-01-20
0.3.0	3 / 3	2016-01-19
0.2.1	2 / 3	2015-11-23
0.2.0	2 / 3	2015-11-11
0.1.0	2 / 3	2015-11-10

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

2 findings

HIGH Publisher changed: trysound → lukastaegert (on 2018-09-16) provenance

This version was published by a different npm account than previous versions on 2018-09-16. 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.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

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: victorystick → trysound (on 2016-08-17) provenance

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

v0.7.7

1 finding

LOW No provenance attestation provenance

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

v0.7.6

1 finding

LOW No provenance attestation provenance

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

v0.7.5

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

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