@asicupv/paella-extra-plugins
Extra plugins for Paella Player.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:marked-alert | AI (phantom-deps): Referenced in build/config files only; not a runtime import gap for this package. | ai | |
| phantom-deps | phantom-dep:marked-emoji | AI (phantom-deps): Referenced in build/config files only; not a runtime import gap for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.9.2 | 5 / 6 | |
| 2.9.1 | 5 / 6 | |
| 2.9.0 | 5 / 5 | |
| 2.8.7 | 5 / 5 | |
| 2.8.6 | 5 / 4 | |
| 2.8.5 | 5 / 4 | |
| 2.8.4 | 5 / 4 | |
| 2.8.3 | 5 / 4 | |
| 2.8.2 | 5 / 4 | |
| 2.8.1 | 5 / 4 | |
| 2.8.0 | 5 / 4 | |
| 2.7.1 | 5 / 4 | |
| 2.7.0 | 5 / 4 | |
| 2.6.0 | 5 / 4 | |
| 2.5.0 | 5 / 4 |
v2.9.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ferserc1) than the most recent previously approved version (miesgre) on 2026-06-04, but ferserc1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ferserc1) than the most recent previously approved version (miesgre) on 2025-10-24, but ferserc1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.8.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ferserc1) than the most recent previously approved version (miesgre) on 2025-10-23, but ferserc1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.8.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ferserc1) than the most recent previously approved version (miesgre) on 2025-10-23, but ferserc1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.8.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ferserc1) than the most recent previously approved version (miesgre) on 2025-10-03, but ferserc1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.8.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ferserc1) than the most recent previously approved version (miesgre) on 2025-09-12, but ferserc1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.