@everymatrix/general-player-forgot-password-form
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:components/GeneralPlayerForgotPasswordForm-DKxXfeUA.js | AI (source-diff): Bundled UI component with fetch calls and Vaadin dev-mode Function(); not malicious. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerForgotPasswordForm-DKxXfeUA.js | AI (source-diff): Standard bundled Svelte component output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerForgotPasswordForm-CH258Cnx.cjs | AI (source-diff): Standard bundled Svelte component output; stable pattern for this package. | ai | |
| source-diff | net-exec-file:components/GeneralPlayerForgotPasswordForm-CH258Cnx.cjs | AI (source-diff): Bundled UI component with fetch calls and Vaadin dev-mode Function(); not malicious. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerForgotPasswordForm-D3qqvJjz.js | AI (source-diff): Standard bundled Svelte component output; stable pattern for this package. | ai | |
| source-diff | net-exec-file:components/GeneralPlayerForgotPasswordForm-D3qqvJjz.js | AI (source-diff): Bundled UI component with fetch calls and Vaadin dev-mode Function(); not malicious. | ai | |
| source-diff | net-exec-file:components/GeneralPlayerForgotPasswordForm-saM-JFFv.js | AI (source-diff): Network calls and dynamic code in Svelte runtime; expected for this UI component package. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerForgotPasswordForm-Bu7zIluH.cjs | AI (source-diff): Standard minified Svelte/Stencil build output; not obfuscated malware. | ai | |
| source-diff | net-exec-file:components/GeneralPlayerForgotPasswordForm-Bu7zIluH.cjs | AI (source-diff): Network calls and dynamic code in Svelte runtime/Vaadin dev-mode detector; expected for this UI component package. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerForgotPasswordForm--cR9clKm.js | AI (source-diff): Standard minified Svelte build output; not obfuscated malware. | ai | |
| source-diff | net-exec-file:components/GeneralPlayerForgotPasswordForm--cR9clKm.js | AI (source-diff): Network calls and dynamic code in Svelte runtime; expected for this UI component package. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerForgotPasswordForm-saM-JFFv.js | AI (source-diff): Standard minified Svelte build output; not obfuscated malware. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires inside bundled Vaadin dev-mode detection code; stable build artifact pattern for this Stencil component package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Large scoped org with 1018 versions; dormancy likely reflects release cadence, not account takeover. | ai |
Versions (showing 34 of 236)
| Version | Deps | Published |
|---|---|---|
| 1.52.2 | 0 / 0 | |
| 1.52.1 | 0 / 0 | |
| 1.52.0 | 0 / 0 | |
| 1.51.0 | 0 / 0 | |
| 1.50.1 | 0 / 0 | |
| 1.50.0 | 0 / 0 | |
| 1.49.2 | 0 / 0 | |
| 1.49.1 | 0 / 0 | |
| 1.49.0 | 0 / 0 | |
| 1.48.2 | 0 / 0 | |
| 1.48.1 | 0 / 0 | |
| 1.48.0 | 0 / 0 | |
| 1.47.3 | 0 / 0 | |
| 1.47.2 | 0 / 0 | |
| 1.47.1 | 0 / 0 | |
| 1.47.0 | 0 / 0 | |
| 1.46.1 | 0 / 0 | |
| 1.46.0 | 0 / 0 | |
| 1.45.14 | 0 / 0 | |
| 1.45.13 | 0 / 0 | |
| 1.45.11 | 0 / 0 | |
| 1.45.10 | 0 / 0 | |
| 1.45.9 | 0 / 0 | |
| 1.45.8 | 0 / 0 | |
| 1.45.7 | 0 / 0 | |
| 1.45.6 | 0 / 0 | |
| 1.45.5 | 0 / 0 | |
| 1.45.4 | 0 / 0 | |
| 1.45.3 | 0 / 0 | |
| 1.45.2 | 0 / 0 | |
| 1.45.0 | 0 / 0 | |
| 1.0.72 | 0 / 0 | |
| 1.0.71 | 0 / 0 | |
| 1.0.70 | 0 / 0 |
v1.52.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.