@pi-r/rollup
Rollup transform function for E-mc.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @e-mc/types is a types package from the same trusted namespace already used by this package; not a suspicious dependency addition. | ai | |
| dependencies | unvetted-dep:@e-mc/types | AI (dependencies): Same author/org as this package; stable internal dependency across versions. | ai | |
| dependencies | unvetted-dep:@e-mc/document | AI (dependencies): Same author/org as this package; stable internal dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 60 versions; no provenance is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:rollup | AI (phantom-deps): rollup is a peer/config dependency; not directly imported in source but legitimately declared. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 4 / 0 | |
| 0.11.4 | 5 / 0 | |
| 0.11.3 | 5 / 0 | |
| 0.11.2 | 5 / 0 | |
| 0.11.1 | 5 / 0 | |
| 0.11.0 | 5 / 0 | |
| 0.10.5 | 5 / 0 | |
| 0.10.4 | 5 / 0 | |
| 0.10.3 | 5 / 0 | |
| 0.10.2 | 5 / 0 | |
| 0.10.1 | 5 / 0 | |
| 0.10.0 | 5 / 0 | |
| 0.9.6 | 3 / 0 | |
| 0.9.5 | 3 / 0 | |
| 0.8.6 | 3 / 0 | |
| 0.8.5 | 3 / 0 | |
| 0.7.6 | 3 / 0 | |
| 0.6.10 | 3 / 0 |
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.