@frsource/semantic-release-config MIT 51 versions

@frsource/semantic-release-config

npm Repository Homepage

Semantic Release configuration files used across the FRSOURCE organization.

51

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

frsgit

Keywords

semantic-releasesemantic-release config

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@semantic-release/git	AI (phantom-deps): Config package; plugins declared as deps for end-user consumption, not direct imports.	ai	2026/04/29
phantom-deps	phantom-dep:@semantic-release/npm	AI (phantom-deps): Config package; plugins declared as deps for end-user consumption, not direct imports.	ai	2026/04/29
phantom-deps	phantom-dep:@semantic-release/github	AI (phantom-deps): Config package; plugins declared as deps for end-user consumption, not direct imports.	ai	2026/04/29
phantom-deps	phantom-dep:@semantic-release/changelog	AI (phantom-deps): Config package; plugins declared as deps for end-user consumption, not direct imports.	ai	2026/04/29
phantom-deps	phantom-dep:@semantic-release/commit-analyzer	AI (phantom-deps): Config package; plugins declared as deps for end-user consumption, not direct imports.	ai	2026/04/29
phantom-deps	phantom-dep:@semantic-release/release-notes-generator	AI (phantom-deps): Config package; plugins declared as deps for end-user consumption, not direct imports.	ai	2026/04/29

Versions (showing 51 of 53)

View all versions

Version	Deps	Published
1.114.0	6 / 10	2026-05-15
1.113.0	6 / 10	2026-05-11
1.112.0	6 / 10	2026-05-11
1.111.0	6 / 10	2026-05-04
1.110.0	6 / 10	2026-04-27
1.109.0	6 / 10	2026-04-13
1.108.0	6 / 10	2026-04-07
1.107.0	6 / 10	2026-04-06
1.106.0	6 / 10	2026-03-20
1.105.0	6 / 10	2026-03-02
1.104.0	6 / 10	2026-03-02
1.103.0	6 / 10	2026-02-26
1.102.0	6 / 10	2026-02-25
1.101.0	6 / 10	2026-02-25
1.100.0	6 / 10	2025-11-24
1.99.0	6 / 10	2025-11-10
1.98.0	6 / 10	2025-11-03
1.97.0	6 / 10	2025-11-03
1.96.0	6 / 10	2025-10-27
1.95.0	6 / 10	2025-10-20
1.94.0	6 / 10	2025-10-20
1.93.0	6 / 10	2025-10-13
1.92.0	6 / 10	2025-10-13
1.91.0	6 / 10	2025-10-07
1.90.0	6 / 10	2025-10-06
1.89.0	6 / 10	2025-10-06
1.88.0	6 / 10	2025-09-29
1.87.0	6 / 10	2025-09-22
1.86.0	6 / 10	2025-09-21
1.85.0	6 / 10	2025-09-15
1.84.0	6 / 10	2025-09-02
1.83.0	6 / 10	2025-08-18
1.82.0	6 / 10	2025-08-11
1.81.0	6 / 10	2025-08-11
1.80.0	6 / 10	2025-08-01
1.79.0	6 / 10	2025-07-21
1.78.0	6 / 10	2025-07-21
1.77.0	6 / 10	2025-07-14
1.76.0	6 / 10	2025-07-14
1.75.0	6 / 10	2025-07-07
1.74.0	6 / 10	2025-07-07
1.73.0	6 / 10	2025-06-23
1.72.0	6 / 10	2025-06-09
1.71.0	6 / 10	2025-06-01
1.70.0	6 / 10	2025-06-01
1.69.0	6 / 10	2025-05-26
1.68.0	6 / 10	2025-05-26
1.67.0	6 / 10	2025-05-23
1.66.0	6 / 10	2025-05-23
1.65.0	6 / 8	2025-05-23
1.64.0	6 / 8	2025-05-12

v1.114.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.113.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.112.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.111.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.110.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.109.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.108.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.107.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.106.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.105.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.104.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.103.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.102.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.101.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.100.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.99.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.98.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.97.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.96.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.95.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.94.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.93.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.92.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.91.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.90.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.89.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.88.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.87.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.86.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.85.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.84.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.83.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.82.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.81.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.80.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.79.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.78.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.77.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.76.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.75.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.74.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.73.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.72.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.71.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.70.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.69.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.68.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.67.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.66.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.65.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.64.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.