@seniorsistemas/semantic-release-common-config
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@semantic-release/gitlab | AI (phantom-deps): Config dependency; declared and referenced as intended for shareable config. | ai | |
| phantom-deps | phantom-dep:semantic-release-jira-notes | AI (phantom-deps): Config dependency; declared and referenced as intended for shareable config. | ai | |
| phantom-deps | phantom-dep:conventional-changelog-gitmoji-config | AI (phantom-deps): Config dependency; declared and referenced as intended for shareable config. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Requires local gitmoji config/transformer files via path.join — not arbitrary or remote; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@semantic-release/github | AI (phantom-deps): Used as a semantic-release plugin in config, not directly imported via require(); phantom-dep false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 3 / 2 | |
| 2.0.1 | 3 / 2 | |
| 2.0.0 | 3 / 2 | |
| 1.11.1 | 3 / 2 | |
| 1.11.0 | 3 / 2 | |
| 1.10.6 | 4 / 1 | |
| 1.10.5 | 4 / 1 | |
| 1.10.4 | 4 / 1 | |
| 1.10.3 | 4 / 1 | |
| 1.10.2 | 4 / 1 | |
| 1.10.1 | 4 / 1 | |
| 1.10.0 | 4 / 1 | |
| 1.9.1 | 4 / 1 | |
| 1.9.0 | 2 / 3 | |
| 1.8.6 | 6 / 1 | |
| 1.8.5 | 6 / 1 | |
| 1.8.4 | 5 / 1 | |
| 1.8.3 | 6 / 1 | |
| 1.8.2 | 5 / 1 | |
| 1.8.1 | 5 / 2 | |
| 1.8.0 | 4 / 2 | |
| 1.7.1 | 4 / 2 | |
| 1.7.0 | 3 / 2 | |
| 1.6.0 | 3 / 2 |
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.