@pie-players/pie-section-player
Web component for rendering QTI 3.0 assessment sections with passages and items
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/chunks/sre-CXN7ed6H-7db47d5d.js | AI (source-diff): Duplicate SRE bundle chunk; same false positive as sre-0162a7a9.js. | ai | |
| source-diff | obfuscated-file:dist/chunks/sre-CXN7ed6H-7db47d5d.js | AI (source-diff): Duplicate SRE bundle chunk; same false positive as sre-0162a7a9.js. | ai | |
| source-diff | obfuscated-file:dist/chunks/sre-CXN7ed6H-f7f64527.js | AI (source-diff): Minified SRE library chunk; long lines expected. | ai | |
| source-diff | net-exec-file:dist/chunks/sre-CXN7ed6H-f7f64527.js | AI (source-diff): Duplicate SRE bundle chunk; same false-positive rationale as sre-0162a7a9.js. | ai | |
| source-diff | net-exec-file:dist/chunks/module-a516757f.js | AI (source-diff): Rollup/Vite bundle artifact with commonjs shim; not malware. Pattern stable for this package's build output. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-default-tool-loaders | AI (phantom-deps): Same org scope; likely consumed via bundled chunk rather than direct import. Stable false positive. | ai | |
| source-diff | obfuscated-file:dist/chunks/sre-0162a7a9.js | AI (source-diff): Minified third-party library (SRE) in build output; not obfuscation for malicious purposes. | ai | |
| source-diff | net-exec-file:dist/chunks/sre-0162a7a9.js | AI (source-diff): SRE (Speech Rule Engine) math accessibility library bundled by Vite; not malware. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-fixed-player | AI (phantom-deps): Same-org monorepo dependency; indirect import through other @pie-players packages is expected. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-esm-player | AI (phantom-deps): Same-org monorepo dependency; indirect import through other @pie-players packages is expected. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-iife-player | AI (phantom-deps): Same-org monorepo dependency; indirect import through other @pie-players packages is expected. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-inline-player | AI (phantom-deps): Same-org monorepo dependency; indirect import through other @pie-players packages is expected. | ai | |
| source-diff | net-exec-file:dist/module-COIydQYl-2o-TlgiW.js | AI (source-diff): Large Rollup bundle with standard CJS interop stubs; not malware. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-tool-calculator-desmos | AI (phantom-deps): Same-org monorepo sibling; bundled rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-tool-text-to-speech | AI (phantom-deps): Same-org monorepo sibling; bundled rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-tool-tts-inline | AI (phantom-deps): Same-org monorepo sibling; bundled rather than directly imported. | ai | |
| phantom-deps | phantom-dep:daisyui | AI (phantom-deps): CSS framework used in config/styling, not direct imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-item-player | AI (phantom-deps): Internal org package; imported indirectly through re-exports. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-context | AI (phantom-deps): Internal org package; imported indirectly through re-exports. | ai | |
| source-diff | net-exec-file:dist/chunks/module-c1d68911.js | AI (source-diff): Rollup/Vite bundle with standard CJS shim; network+exec pattern is expected for bundled web components. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.3.50 | 5 / 11 | |
| 0.3.49 | 7 / 11 | |
| 0.3.48 | 7 / 11 | |
| 0.3.47 | 8 / 11 | |
| 0.3.46 | 8 / 11 | |
| 0.3.45 | 8 / 11 | |
| 0.3.44 | 8 / 11 | |
| 0.3.43 | 8 / 11 | |
| 0.3.42 | 8 / 11 | |
| 0.3.41 | 8 / 11 | |
| 0.3.40 | 8 / 11 | |
| 0.3.39 | 8 / 11 | |
| 0.3.38 | 8 / 11 | |
| 0.3.37 | 8 / 11 | |
| 0.3.36 | 8 / 11 | |
| 0.3.35 | 8 / 11 | |
| 0.3.34 | 8 / 11 | |
| 0.3.33 | 8 / 11 | |
| 0.3.32 | 8 / 11 | |
| 0.3.31 | 8 / 11 | |
| 0.3.30 | 8 / 11 | |
| 0.3.29 | 8 / 10 | |
| 0.3.28 | 8 / 10 | |
| 0.3.27 | 8 / 10 | |
| 0.3.26 | 8 / 10 | |
| 0.3.25 | 8 / 10 | |
| 0.3.24 | 8 / 10 | |
| 0.3.23 | 8 / 10 | |
| 0.3.22 | 8 / 10 | |
| 0.3.21 | 8 / 10 | |
| 0.3.20 | 8 / 10 | |
| 0.3.19 | 8 / 10 | |
| 0.3.17 | 8 / 10 | |
| 0.3.16 | 8 / 10 | |
| 0.3.13 | 8 / 10 | |
| 0.3.12 | 8 / 10 | |
| 0.3.11 | 8 / 10 | |
| 0.3.10 | 8 / 10 | |
| 0.3.9 | 8 / 10 | |
| 0.3.8 | 5 / 10 | |
| 0.3.7 | 5 / 10 | |
| 0.3.5 | 5 / 10 | |
| 0.3.4 | 5 / 10 | |
| 0.3.3 | 6 / 10 | |
| 0.3.2 | 6 / 10 | |
| 0.3.1 | 6 / 10 | |
| 0.2.12 | 14 / 9 |
v0.3.50
5 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (carlacostea) than the most recent previously approved version (chillenious) on 2026-06-09, but carlacostea 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.
v0.3.49
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.48
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.47
7 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (carlacostea) than the most recent previously approved version (chillenious) on 2026-06-03, but carlacostea 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.
v0.3.46
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.45
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.42
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.41
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.40
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.39
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.38
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.35
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.34
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.23
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.22
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.