@everymatrix/pam-login
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/pam-login/pam-login-6481de59.js | AI (source-diff): Network call is a CSS fetch helper; no dynamic code execution. Benign widget pattern. | ai | |
| source-diff | obfuscated-file:dist/pam-login/pam-login-6481de59.js | AI (source-diff): Minified Stencil bundle with readable login UI strings; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/cjs/pam-login-340b7d1e.js | AI (source-diff): Standard minified Stencil build output; not obfuscated malware. Stable pattern for this package. | ai | |
| source-diff | net-exec-file:dist/cjs/pam-login-340b7d1e.js | AI (source-diff): Network call is a CSS fetch helper; no dynamic code execution (eval/Function). Benign widget pattern. | ai | |
| source-diff | obfuscated-file:dist/esm/pam-login-6481de59.js | AI (source-diff): Standard minified Stencil build output; not obfuscated malware. Stable pattern for this package. | ai | |
| source-diff | net-exec-file:dist/esm/pam-login-6481de59.js | AI (source-diff): Network call is a CSS fetch helper; no dynamic code execution. Benign widget pattern. | ai | |
| source-diff | net-exec-file:dist/pam-login/pam-login-b5708613.js | AI (source-diff): Same CSS fetch + innerHTML pattern; consistent with documented widget styling API. | ai | |
| source-diff | obfuscated-file:dist/cjs/pam-login-6a0adc81.js | AI (source-diff): Standard Stencil.js minified build output for a login widget; not obfuscation. | ai | |
| source-diff | net-exec-file:dist/cjs/pam-login-6a0adc81.js | AI (source-diff): Network calls are CSS URL fetches; dynamic code execution is innerHTML for styling — legitimate widget pattern. | ai | |
| source-diff | obfuscated-file:dist/esm/pam-login-b5708613.js | AI (source-diff): Standard Stencil.js minified ESM build output; not obfuscation. | ai | |
| source-diff | net-exec-file:dist/esm/pam-login-b5708613.js | AI (source-diff): Same CSS fetch + innerHTML pattern as CJS build; legitimate widget behavior. | ai | |
| source-diff | obfuscated-file:dist/pam-login/pam-login-b5708613.js | AI (source-diff): Minified Stencil.js bundle; content is i18n strings and CSS helpers, not obfuscated malware. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped component package; missing metadata is consistent across 292 versions of this org's packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal @everymatrix component; no description is a stable pattern for this org. | ai |
Versions (showing 9 of 216)
| Version | Deps | Published |
|---|---|---|
| 1.73.2 | 0 / 0 | |
| 1.73.1 | 0 / 0 | |
| 1.73.0 | 0 / 0 | |
| 1.72.2 | 0 / 0 | |
| 1.72.1 | 0 / 0 | |
| 1.72.0 | 0 / 0 | |
| 1.71.1 | 0 / 0 | |
| 1.71.0 | 0 / 0 | |
| 1.70.1 | 0 / 0 |
v1.73.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.