@github/catalyst
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/test.js | AI (source-diff): Minified bundled test helper code, not malicious obfuscation; matches package's build tooling. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Routine GitHub-org maintainer rotation, not a compromise pattern. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine GitHub-org maintainer rotation, not a compromise pattern. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.8.1 | 0 / 15 | |
| 1.8.0 | 0 / 15 | |
| 1.7.0 | 0 / 14 | |
| 1.6.0 | 0 / 14 | |
| 1.5.0 | 0 / 14 | |
| 1.4.2 | 0 / 14 | |
| 1.4.1 | 0 / 14 | |
| 1.4.0 | 0 / 14 | |
| 1.3.2 | 0 / 18 | |
| 1.3.1 | 0 / 18 | |
| 1.3.0 | 0 / 18 | |
| 1.2.1 | 0 / 18 | |
| 1.2.0 | 0 / 18 | |
| 1.1.4 | 0 / 17 | |
| 1.1.3 | 0 / 17 | |
| 1.1.2 | 0 / 18 | |
| 1.1.0 | 0 / 18 | |
| 1.0.2 | 0 / 17 | |
| 1.0.1 | 0 / 17 |
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (koddsson) than the most recent previously approved version (keithamus) on 2022-02-25, but koddsson 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.
v1.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (koddsson) than the most recent previously approved version (keithamus) on 2022-02-11, but koddsson 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.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (koddsson) than the most recent previously approved version (keithamus) on 2021-08-05, but koddsson 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.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 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.
v1.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (keithamus) than the most recent previously approved version (koddsson) on 2020-11-24, but keithamus 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.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.