@economist/component-grid
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/example.js | AI (source-diff): Long-line React.createElement demo output, not obfuscation; no malicious behavior. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Change occurred in 2016; long-stable, self-flagged as inconsistent with active takeover. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Historical publisher change, stable for years; not a fresh signal. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 0 / 51 | |
| 1.3.3 | 1 / 53 | |
| 1.3.2 | 1 / 44 | |
| 1.3.1 | 0 / 26 | |
| 1.3.0 | 0 / 25 | |
| 1.2.2 | 0 / 25 | |
| 1.2.1 | 0 / 25 | |
| 1.2.0 | 0 / 25 | |
| 1.1.1 | 1 / 24 | |
| 1.1.0 | 1 / 24 | |
| 1.0.0 | 1 / 24 |
v1.3.3
3 findingsNewly 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-05-16, 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.3.2
3 findingsNewly 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-31, 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.3.1
2 findingsThis version was published by a different npm account (fabiosantoscode) than the most recent previously approved version (economist) on 2016-01-18. It has since remained available on npm for 3837 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.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.