@economist/component-picture
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 | obfuscated-file:lib/element-resize-listener.js | AI (source-diff): Babel-compiled build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:lib/example.js | AI (source-diff): Compiled example file with inline sourcemap, not obfuscated. | ai | |
| source-diff | obfuscated-file:lib/index.js | AI (source-diff): Compiled lib output matching src/index.js build. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): 2015 publisher change, live unremoved for 10+ years; stale historical event, not active takeover. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Same stale 2015 publisher change; not a fresh signal. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 1 / 55 | |
| 1.2.1 | 2 / 45 | |
| 1.2.0 | 2 / 45 | |
| 1.1.0 | 2 / 26 | |
| 1.0.0 | 2 / 25 |
v1.2.1
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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (economist-org-bot) than the most recent previously approved version (economist) on 2016-03-29, but economist-org-bot is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.0
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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (economist-org-bot) than the most recent previously approved version (economist) on 2016-03-23, but economist-org-bot is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.0
2 findingsThis version was published by a different npm account (sebinsua) than the most recent previously approved version (economist) on 2015-11-23. It has since remained available on npm for 3893 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.